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

Re: How to repair a broken Revision in our SVN-Repository

From: Blair Zajac <blair_at_orcaware.com>
Date: Wed, 24 Jun 2009 09:11:32 -0700

On Jun 23, 2009, at 11:12 PM, Malte Finsterwalder wrote:

> Blair Zajac wrote:
>> Malte Finsterwalder wrote:
>>> Maybe some addition information about the problem can help.
>>> When I do:
>>> svn log -r 8831 http://repositoryUrl
>>> I get:
>>> svn: REPORT of '/oosetb/!svn/bc/8831': 200 OK (http://ooseappsrv)
>> You should run svnadmin verify on the repository to see if it's
>> truly a bad
>> revision or if something else is going on.
> svnadmin gives the same error:
> We ran svn in the german version on the server, which gives:
> * Revision 8830 verifiziert.
> svnadmin: Kann Längenzeile nicht aus Datei »oosetb\db\revprops\8831«
> lesen
> Which is translated roughly to:
> * Revision 8830 verified.
> svnadmin: Can't read length-line from file »oosetb\db\revprops\8831«
> Which is probably similar to the error I got reviously: Premature
> end of
> file.
> It's no problem, that the information from that broken revision is
> lost.
> I just would like to fix it up in a way that it doesn't disturb
> svn-operations.
> Any idea how I can fix the problem?

You can try the fsfsverify.py script.


If that doesn't work, there's either calling CollabNet for help and
paying for support or recovering a repository from backups to the
previous revision and then putting the commits in there manually.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-24 18:12:36 CEST

This is an archived mail posted to the Subversion Users mailing list.