[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DB corruption of first day of subversion

From: Alex R. Mosteo <alejandro_at_mosteo.com>
Date: 2004-11-11 17:42:32 CET

Mark wrote:
> Nearly all "corruption" issues with BDB are permissions issues that are
> easily avoided by following the documentation's instructions and easily
> corrected. Of the rest, almost all is caused by running outdated versions of
> BDB, esp 4.1 on OSX, and running BDB databases on network filesystems.

Well, you have just listed some caveats which may go unnoticed for some
time by a newcomer. I was using 4.2 on linux on a local drive. I don't
compile subversion myself, I use the precompiled .rpm from subversion
homepage... so I suppose these have the dependencies right.

> Maybe FSFS is more highly stable, but it's got nowhere the exposure of the
> BDB FS, so judging the backends by search hits on this list for corruption
> isn't a super good idea.

Maybe. My own stress test cases regularly make fail the BDB repository
but have no effect in the FSFS repository. Obviously my choice is
between using a proven wrong BDB or a FSFS with unknown bugs. Which
isn't really a choice since I'm obliged to use FSFS and hope that if
some FSFS nasty bug arises my backup is not too old.

Of course YMMV, but both my personal experience and my following of this
list for several months hint to avoid BDB. And now we have a new 4.3
release of BDB which has still less exposure than FSF.

So: In any case, backup often ;)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 11 17:39:58 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.