[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 12:14:35 CET

Ritesh Nadhani wrote:
> Hello,
> ----- Original Message ----- From: "Alex R. Mosteo" <alejandro@mosteo.com>
>> - Avoid BerkeleyDB
> Even I am use BerkelyDB. Do you say I should use FSFS?

I have had problems with BDB. I haven't had problems with FSFS. It's
only my experience, but if I remember well, I still haven't heard a
single complaint of corruption from someone using FSFS. From BDB,
instead, you can find aplenty.

>> - Try some humongous imports/exports/commits/updates with lots of files.
> The funny part is that it was doing ok with 2-3 commits for around 1
> day. After that I did one full checkout and one full commit from my home
> machine to the server and then it started failing everytime. The
> checkout was of around 10MB (it included doxygen documentation for the
> whole source code). Do you think that might be the reason and I move to

"Failing everytime". What that means? In my case, the repository seemed
locked forever and coulnd't be recovered. What I mean is that there
weren't error messages after the one in the first failure, nor
progressive corruption... A failed commit and then nothing in any operation.

>> - Make backups :)
> For this to happen, my subversion has to work for atleast one week :)

That's the same period I use.

My bottom line: if you haven't any special reason to use BDB, give FSFS
a try.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 11 12:12:05 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.