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

Re: svnadmin: Can't read length line in file ...

From: John Szakmeister <john_at_szakmeister.net>
Date: 2006-05-23 10:46:47 CEST

----- Mark Junker <m.junker@hm-software.de> wrote:
> John Szakmeister schrieb:
> > No, using them both doesn't necessarily trigger the issue. It
> appears that mod_dav_svn alone can do it. I've been keeping track of
> this issue, and every one that I have ever seen has been a result of
> mod_dav_svn.
> >
> > [snip]
> >> I also think that this is a serious issue but the only thing we
> have
> >> in
> >> common is the FSFS repository. Maybe I should convert it to BDB?
> >
> > BDB is a good backend, but you really need to be careful about how
> you set it up. FSFS is far easier to manage/maintain. The good news
> is that this particular problem is recoverable. All the data is
> there, you just have to know how to put it together. I have a script
> that can do just that.
> Can you please send me this script?

Here it is.

> BTW: What's the reason for not publishing this script?

I have pushed it out to the list before (it's not like I'm keeping it a secret). The biggest reasons for not publishing it are:
 1) I'm not maintaining it.
 2) It's not very well written--the whole thing was developed "on the fly" to help troublesoot this read line length error in situations where I didn't have access to the repository nor the rev file.
 3) Figuring out the logical place to host it. I don't think it belongs in Subversion's code base, especially since I'm not maintaining it.

I don't have much time for extracurricular activities these days, so I haven't spent much time trying to figure out answers to the above. If there's enough interest, perhaps I'll look at hosting it on my site.

To use it, run:
  fsfsverify.py -f /path/to/repos/db/revs/corrupted-rev-file

Note that this script comes with no warranty. You're entirely on your own if it eats your repository. :-) Make sure to work from a backup!

With all of that said, I've been able to recover every instance of this that I've come across with the exception of a couple before Malcome really helped narrow down the algorithm behind the corruption.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Tue May 23 10:48:18 2006

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.