Re: fsverify.py unable to fix invalid svndiff header

>>>>> Stefan Sperling <stsp_at_elego.de>:

> Steinar, I'm sorry we can't help quickly here. At the moment I have no time
> to look at this further. I hope you have a good backup you can restore from.

No luck there I'm afraid.

I have backups, but either they are too old to be of interest, or they
are corrupted as well. The corruption isn't new.

The repository was created by converting an existing CVS repository in
May 2007, the repository was converted from BDB to FSFS in February 2009
(using svnadmin dump and load), and the corrupted revision is from
December 2005.

See repository history and details the end of the original article:
 http://thread.gmane.org/gmane.comp.version-control.subversion.user/104232
 nntp://news.gmane.org/gmane.comp.version-control.subversion.user/104232

Anyway, from the history of the repository, I'm guessing the svnadmin
load of February 2009 is the most likely culprit...? I don't know if
that helps anything.

I've been looking to see if there are any tools that can slurp out the
history of a repository, using the svn client API. But all repository
conversion seems to be based on "svnadmin dump". And "svnadmin dump"
croaks on all revisions later than 682...:-/
Received on 2011-05-18 22:10:21 CEST