Joshua Wehner wrote:
> Hi all --
> I seem to be at a dead end. I'm having a problem with my subversion
> repository. (I'm running it on a Mac.) It started after a recent reboot
> (which hung, and required a hard-restart).
> First, I got 500 Internal Server Errors when trying to check-in. The
> server log said, "Berkeley DB error while checkpointing after Berkeley
> DB transaction for filesystem /Volumes/Data/svnrepo/db:\nInvalid
> argument [500, #160029]"
> So, I google a bit and tried to recover the repository.
> # svnadmin recover /Volumes/Data/svnrepo
> Please wait; recovering the repository may take some time...
> subversion/libsvn_fs/bdb/bdb-err.c:51: (apr_err=160029)
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> The SVN Book doesn't really cover this. It sort of assumes that the
> recovery will work. So, I googled a little bit, and... At this point
> (this may not have been wise, I realize) I decided to copy over a
> back-up of the repository, made about a month ago.
> Now, when trying to interract with the database, I get this message:
> $ svn update
> svn: REPORT request failed on '/svn/!svn/vcc/default'
> svn: Reference to non-existent revision '231' in filesystem
> What now?
That last error is perfectly expected, since your working copy thinks it is
at a later revision than actually exists in the repository.
Regarding recovering your problem repository:
First, make a backup tarball of the problem repository.
Then, try running "db_recover -v -c" from within the db subdir of the
problem repository (Having made sure no other processes will try to access
If that doesn't clear things up, then:
Join #svn on irc.freenode.net, and get in touch with me (maxb) for some
Put the tarball on a web/ftp site and email me the URL.
Email full output of "db_recover -v -c" here.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jan 11 17:35:57 2005