Hi All,
I'm also expiencing the same problems described in issue 2056. One of my
repositories gets wedged on a almost daily basis.
I'm about to upgrade to subversion 1.1.1 to see if that fixes the problem,
but I see that issue 2056 is still open.
Here are some of the details:
svnadmin, version 1.1.0 (r11180)
compiled Oct 20 2004, 21:44:46
BDB 4.2.52
Linux 2.4.27.
Apache HTTP 2.0.52
Repository access is apache only. No svnserv or local access.
The output of db_stat is:
[fish@nurgle src]# db_stat -h /home/svn/2.0/db -c
18453 Last allocated locker ID.
2147M Current maximum unused locker ID.
9 Number of lock modes.
2000 Maximum number of locks possible.
2000 Maximum number of lockers possible.
2000 Maximum number of lock objects possible.
994 Number of current locks.
1002 Maximum number of locks at any one time.
1985 Number of current lockers.
2000 Maximum number of lockers at any one time.
11 Number of current lock objects.
62 Maximum number of lock objects at any one time.
538868 Total number of locks requested.
536879 Total number of locks released.
0 Total number of lock requests failing because DB_LOCK_NOWAIT was
set.
0 Total number of locks not immediately available due to conflicts.
0 Number of deadlocks.
0 Lock timeout value.
0 Number of locks that have timed out.
0 Transaction timeout value.
0 Number of transactions that have timed out.
720KB The size of the lock region..
0 The number of region locks granted after waiting.
721431 The number of region locks granted without waiting.
And the Repository URL is at http://svn.neostats.net/svn/2.0
Anything else you need to help you reproduce the problem?
Thanks
Justin Hammond
(I'm subscribed via digest version, so for quick replies, please CC me
directly as well on this issue)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 07:08:42 2004