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

Recovery from a broken repository

From: Rob Kendrick <rjek_at_rjek.com>
Date: 2005-03-07 23:18:18 CET


My Subversion repository recently stopped working in the past few days (a
replacement set of discs have been installed in the server it resides on, data
was rsynced from one set to the other over a network, if that matters.):

svn@pike:~$ svnlook info svn
svn: No transaction named '3r' in filesystem 'svn/db'

11 rjek_at_trite:~ $ svn co svn://svn.rjek.com/colloquy
svn: No transaction named '3r' in filesystem '/home/svn/svn/db'

svn@pike:~$ svnadmin dump svn > dump
* Dumped revision 0.
svn: No such string '1yq'

(at which point only a few files are dumped, most of them havn't changed since
the repository was created.)

svn@pike:~$ svnadmin recover svn/
Repository lock acquired.
Please wait; recovering the repository may take some time...

Recovery completed.
The latest repos revision is 79.

(and it doesn't help at all.)

The repository is only small (80 or so changes, all of 5MB as a tar.bz2,
berkeley db format), and I have a copy of the head (no branches or anything)
but losing the change information is vexing.

Has anybody any suggestions for what to try next? If anybody would like to
examine a copy of the repository, there's nothing secret in it, and I'm welcome
to put a tarball of it up somewhere if people think it might help.

Thanks for your time,

Rob Kendrick
PGP signed or encrypted mail welcome (Key ID: 3651D17A)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 7 23:18:40 2005

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.