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

Re: Severe repository database corruption

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-02 00:45:02 CEST

On Thu, 2004-07-01 at 17:34, Frank Freund wrote:

> > linux: # svnadmin recover /usr/local/apache2/svn
> > Please wait; recovering the repository may take some time...
> > Recovery completed.
> > The latest repos revision is 394.
> which looked fine, but didn't worked - same errors as above.

What do you mean it didn't work? It *did* work, the repository was

Did it get 'stuck' again when you tried to access it? If so, it's
probably because you ran recovery as the root user, which messed up all
the permissions.

Have you read this FAQ?


If 'svnadmin recover' doesn't work, then use the catastrophic flag to
db_recover. ('db_recover -vec -h repos/db/'). Then make sure all the
permissions are set correctly before restarting apache. That is, make
sure apache has full read/write access to the whole repository (even
better if apache owns the repository) before starting it again. If the
repository has weird ownership or permissions, then the repository will
get 'stuck' again when apache tries to open it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 2 00:47:57 2004

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.