You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Douglas Stetner <dg...@maths.uq.edu.au> on 2004/02/20 02:31:52 UTC

svnadmin recover fails

Hi,

I have run into a corrupt database, and the manual says:

>If the previous procedure, for some reason, does not successfully
>unwedge your repository, you should do two things. First, move your
>broken repository out of the way and restore your latest backup of it.
>Then, send an email to the Subversion developer list (at
><de...@subversion.tigris.org>) describing your problem in detail. Data
>integrity is an extremely high priority to the Subversion developers. 

So here is my report....

I am using version (from fink on Mac OSX 10.3.2)

> i      svn-ssl 0.37.0-12       Compelling replacement for CVS -
> svnserve, tools (with SSL)

with 

> i      db42-ssl        4.2.52-12       Berkeley DB embedded database - ssl
> i      db42-ssl-bin    4.2.52-12       Binary utilities for db42-ssl
> i      db42-ssl-doc    4.2.52-12       Documentation for db42-ssl
>        db42-ssl-java   4.2.52-12       Berkeley DB java libraries - ssl
> i      db42-ssl-shlibs 4.2.52-12       Shared Libraries for db42-ssl


>$ svn list file:///Users/stetner/SVN_REPOSITORY.old/
>svn: Berkeley DB error while checkpointing after Berkeley DB
>transaction for filesystem /Users/stetner/SVN_REPOSITORY.old/db:
>Invalid argument
>
>$ svnadmin recover SVN_REPOSITORY.old 
>Please wait; recovering the repository may take some time...
>svn: DB_RUNRECOVERY: Fatal error, run database recovery



I have since done a dump (of the 'corrupt' db) and load into a new
repository with no problems.

Cheers,
Doug
-- 
Douglas Stetner                                   <ds...@bigpond.net.au>

"Prediction is difficult, especially the future."
                                                  - Niels Bohr.

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


Re: svnadmin recover fails

Posted by John Szakmeister <jo...@szakmeister.net>.
On Thursday 19 February 2004 21:31, Douglas Stetner wrote:
> [snip]
>
> I am using version (from fink on Mac OSX 10.3.2)
>
> > i      svn-ssl 0.37.0-12       Compelling replacement for CVS -
> > svnserve, tools (with SSL)
>
> with
>
> > i      db42-ssl        4.2.52-12       Berkeley DB embedded database -
> > ssl i      db42-ssl-bin    4.2.52-12       Binary utilities for db42-ssl
> > i      db42-ssl-doc    4.2.52-12       Documentation for db42-ssl
> > db42-ssl-java   4.2.52-12       Berkeley DB java libraries - ssl i     
> > db42-ssl-shlibs 4.2.52-12       Shared Libraries for db42-ssl
> >
> >
> >$ svn list file:///Users/stetner/SVN_REPOSITORY.old/
> >svn: Berkeley DB error while checkpointing after Berkeley DB
> >transaction for filesystem /Users/stetner/SVN_REPOSITORY.old/db:
> >Invalid argument
> >
> >$ svnadmin recover SVN_REPOSITORY.old
> >Please wait; recovering the repository may take some time...
> >svn: DB_RUNRECOVERY: Fatal error, run database recovery

Two questions.  Is access using 'file:///' the only way your accessing the 
repository?  IOW, are you using httpd, or svnserve to access at all?  If you 
you really need to check out the book on using multiple servers.

Secondly, did you run recover as the user who owns the repository?  I've seen 
this problem if you run as a user who has read access to repository, but 
doesn't have write access (I believe that was the situation... it's been a 
while).  It ends up telling you to run recover again, instead of the more 
intuitive 'permission denied' error.

And, as always, make sure you don't have any other server processes touching 
the repository while you're running recover.

-John

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