On 5/28/06, Alex Le Dain <alex@psi.com.au> wrote:
[snip]
> All these errors are relatively benign, the server process did not exit.
> I then ran two copies of the spamming batch file, one on the server
> machine and one from another machine. I still wasn't able to crash the
> server, but there were a lot of the same 'Resource Device' types of
> errors. Making a repository using the fsfs database did not exhibit the
> problems.
>
> According to the tigris site I need a buddy to register this as a bug.
> Can anyone verify these faults and help me add the bug?
>
I've had rare sporadic crashes in the test suite with BDB, but since
they were not consistently reproduceable and I don't use BDB, I
haven't tried to chase them down. If you can provide a full batch
script to create the repo, stress it, etc to repro it, I'll try it out
on BDB 4.4.20 and Subversion trunk on Win32.
Personally, I found in the past (and why I switched to fsfs) that BDB
is sensitive to load based on its config parameters -- the Subversion
defaults used to be pretty low (it was a year or two ago and I'm not
sure about that anymore) and I had to tweak the parameters in the
DB_CONFIG file to fit load in regards to number of locks, lock memory,
etc. I don't remember all the details but they are doc'd in BDB
somewhere and I would often get errors somewhat similar to what you've
reported if I hit a BDB Subversion database hard and caused it to
croak because it hit some limit. Recovery usually brought it back to
life with no data loss. But fsfs has been far simpler and easier to
use and maintain for me (having very little experience with BDB).
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 29 06:04:36 2006