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

Re: svnadmin recover fails

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-02-21 13:02:10 CET

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.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 21 13:03:42 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.