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

RE: Reliability: CVS vs. SVN

From: Jim Mochel <jim.mochel_at_ascentialsoftware.com>
Date: 2005-02-10 14:59:54 CET

Myself and another developer have been supporting about 3/4 Gig of
source/data across 8 repositories for two months now and we have yet to
encounter any corruption of the database. (We did have a easily fixable
locking problem due to how we were backing up the repositories). We are
using the Berkeley DB as the back end, not the FS store.

My experience is that invalid states of some kind happens about as often
with CVS or SVN (though usually on the client side) BUT you know about it
almost instantly with SVN and have an easy time fixing it.

It happened even less with ClearCase for me, but when it got confused,
recovery was not an option.

Jim Mochel

-----Original Message-----
From: Joakim Simonsson [mailto:joakim@autosim.no]
Sent: Thursday, February 10, 2005 3:52 AM
To: users@subversion.tigris.org
Subject: Reliability: CVS vs. SVN

Question1:

When using svnserve, is it then possible corrupt the repository?

Question2:

Is it more easy to corrupt a SVN repository than a CVS repository?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 10 15:03:41 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.