> > In short, I'm a bit stumped. I think we need more real data (the output
> > from your tool is useful, but it only goes so far). What I'd really
> > like is a complete un-recovered repository, and possibly an uncorrupted
> > copy of the corrupt revision's file if possible. And a pony.
> I'd like that as well. I can work with one guy to get you access to a
> complete, un-recovered repository, but he doesn't have an uncorrupted copy of
> the file in question. :-( I'm not sure it's worth the trouble unless we can
> tickle the failure ourselves, and I don't believe we'll be able to do that
> without an uncorrupted copy of the file.
Have either of you thought about the fact that the cause may not be
fsfs, but the (new) xdelta code generating svndiffs? Maybe even looked
into that already? The fact that we don't get any reports for BDB
might be because you can't easily look into a bdb-rev.
Received on Sat Dec 3 15:15:53 2005
This is an archived mail posted to the Subversion Dev