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

Re: Database Corruption in SVN

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Sun, 13 Nov 2011 02:52:25 -0500

On Fri, Nov 11, 2011 at 6:18 AM, Waseem Shahzad
<waseem.shahzad_at_curemd.com> wrote:
> Is there any way that SVN database may be corrupted. Any story , Issue ,
> Experience….

Define "corrupted". Leaving write access to local users, such as is
common with "file:///" based access, is begging for someone to screw
up your repository with a command line mistake. And "split-brain"
problems when you try to replicate repositories for high availability
but don't quite get it right are not unheard of. There's also the
problem I had early in my career when I tried to replicate a
repository with a lot of debris cleared out of it but kept the same
uuid. That caused serious pain.

Also, bad disks and file system problems could corrupt the database.
Losing a revision to bad blocks on your disk is a very real risk,
which is another reason to do good backups. And that is true of *any*
database without exceptional redundancy and error checking internal to
Received on 2011-11-13 08:54:56 CET

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.