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

What are the causes of DB corruption?

From: David Coppit <subversion_at_coppit.org>
Date: 2005-02-03 04:32:59 CET

My database keeps getting corrupted, which is extremely disconcerting
given the importance of the data I want to store in it. svnadmin recover
fails, as does svnadmin dump. My only option seems to be to restore from

Can someone please enumerate all the possible causes of DB corruption?

My developers are accessing the repository using svn+ssh. I've created a
wrapper for the svn command to set the umask properly, and have asked all
the users to modify their .cshrc to set their PATH to include my bin
directory before /usr/bin. (I think that works for ssh tunnels, right?)

The repository is on a local /scratch disk, and I'm running hot-backup.py
after every commit.

- Do I have do lock access to the repository somehow while hot-backup.py
   is running?

- Do I have to worry about our version of subversion? Or the OS?
   (subversion-1.0.0-73.14 on SuSe)

- What about subclipse with the JavaSVN bindings? Any risks there?

- Do I have to worry about different client versions accessing svnserve?

- Do I have to worry about different shared libraries on different
   machines in our department?

Short of sitting next to them when they corrupt the repository, is there
any way that I can debug this?

Thanks for the help. I really like subversion, but if I can't get it
stable, I'm going to have to go back to CVS (**shiver**).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 3 04:35:19 2005

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.