"Data integrity is an extremely high priority to the Subversion
developers".

If this is true, why in the name of all that is good is the following
line in the default DB_CONFIG file?

set_flags DB_LOG_AUTOREMOVE

I'm extremely surprised that Subversion, by default, cannot recover
from a simple system hang (because Berkley DB cannot). Of course, this
is personal, since it happened to me after using Subversion for about
two weeks. I went to do my first backup, and to my surprise found my DB
corrupted, and there were no logs to do a recovery with because they
had been removed.

Saving me 15MB of disk space so that I can waste hours of my time
instead is hardly cost effective. Please, PLEASE, change this back ASAP
so that other people, like me, aren't burned the first time their
system hangs. Users should have to do something to make their systems
brittle. From the factory, it should be rock solid.

Otherwise, I love Subversion and am very happy with the quality and
design. This is a project worth continuing.

Sincerely,

Eric Ocean

P.s. I can access the svn repository, but the "dump" file generated by
svnadmin is corrupt and won't load past revision 3 (I'm currently
around revision 40), so creating a new repository is out. Yes, I've
tried db_recover. It fails, and according to Sleepycat, the only thing
that would work is a catastrophic recovery which requires complete log
files. In my world, "catastrophic" refers to permanent hardware
failure, not system hangs. Oh well.