Bug#252974:

[Max Bowsher]

Hi, I'm an upstream Subversion developer, adding a few comments to this 
discussion.

I agree that converting to FSFS is a workaround, not a fix.
However, there is not enough information in this bug report as-is for anyone 
to do anything useful with it.

High volume of activity alone is certainly not the cause of problems, since 
there are some giant active BDB repositories in use - the ASF's, for one.

Regarding trying to move forward with this bug, I suggest the first thing to 
do is to post the errors produced with a current version of Subversion. 
Versions 1.1.0 and later have much improved verbosity of BDB error messages, 
over the 1.0.x series.

Also, I'd suggest reviewing the permissions set on the repositories, and 
considering the umask of the accessing processes - sporadic semi-regular 
wedging of a BDB repository could be indicative that when a new database 
logfile is created, it is being created without group-write perms (due to 
the umask), thus barring access to processes relying on group privs for 
access.
Please show "ls -lR repository" output for a repository in a problem state.

Another thing that would be useful to know is what access methods are being 
used - exclusively http? or other accessors too, besides apache?

Thanks,
Max.