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

Re: Anti-FUD: SVN ate my repository

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-09-21 14:57:54 CEST

Gregory Burd <gburd@sleepycat.com> wrote on 09/21/2004 08:49:43 AM:

> wedged repository, n:
> A repository in need of repair using available recovery tools.
> Processing cannot continue until the underlying database has been
> rebuilt from the available database log files.

As a user this definition would scare me because of the word "rebuilt".
What if I do not have all of the log files it needs, etc...? Also, I
think this is actually what the svn devs refer to as a "catastrophic
recovery" but could be wrong, as it sounds like you are referring to the
db_recover process as opposed to what svnadmin recover does. I think a
wedged repository is a bit simpler to fix than this.

> corrupted repository, n:
> A repository with unexpected data within the database and a lack of
> sufficient database log files to effect proper recovery. Proper
> administration of Subversion database resources should prevent this
> from ever happening. Please read the "How to Properly Maintain
> Backups" reference guide for more information.

I would agree that this is probably what a svn dev considers a corrupted
repository. This definition should likely include something indicating
how rare this situation would be, and what factors might likely cause it,
such as bad hardware or ignoring the warning about using networked file


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 21 14:58:13 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.