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

Re: DB corruption

From: <azverkan_at_yahoo.com>
Date: 2003-01-26 20:58:02 CET

skutsje# svnadmin recover /data3/subversion/repos
        Acquiring exclusive lock on repository db, and running recovery procedures.
        Please stand by...svn: Unsupported repository version
        svn: Expected version '1' of repository; found no version at all; is
        `/data3/subversion/repos' a valid repository path?
        svn: No such file or directory
        svn: svn_io_file_open: can't open `/data3/subversion/repos/format'
skutsje# cat /data3/subversion/repos/format
        1

Thinking what the fuck - and doing it a second time gives:

skutsje# svnadmin recover /data3/subversion/repos
        Acquiring exclusive lock on repository db, and running recovery
        procedures.
        Please stand by...
        Recovery completed.
        The latest repos revision is 52.

And after a fair chunk of chmod/chown's things on the DB are fine and
dandy again.

  

I believe the second time works when the first time fails because the
first time it upgrades your repository to the latest version and then
the second time completes the recover. I've seen this before when I
upgraded from db-4.0 to db-4.1 and forgot to run db_upgrade.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:18:12 2006

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