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

possible mechanism of repo corruption

From: Matthew Beals <mjbeals_at_mtu.edu>
Date: Thu, 9 Jun 2011 09:48:18 -0400 (EDT)

I just suffered a fairly major repo corruption problem. Fortunately I had nightly dumps to restore from as well as an updated working copy of the affected repos, so the only thing I lost was some file history. Now I'm trying to figure out what caused the issue and if I can prevent it in the future.

I have two areas of concern:

1. The repos are stored on our RAID and accessed over NFS mounted with the nolock option. I've read that this isn't a concern with the fsfs backend, but I'm still worried this had something to do with it.

2. We access the repos over both dav_svn and ssh spawning svnserve (using the wrapper script to set umask to 002). I auth apache through pam, so uid/gid is identical for both methods for all users. These repos were stable for a solid year with no problems using only dav_svn. I only introduced svnserve recently to make accessing the repos from outside the firewall easier with tortiseSVN and one month later....broken repos.

Is any of this considered bad practice that could lead to repo corruption?

Received on 2011-06-09 15:48:54 CEST

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.