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

Re: Lack of Subversion repository recovery tools

From: Andreas Hasenack <andreas_at_mandriva.com.br>
Date: 2007-07-04 14:17:48 CEST

On Wed, Jul 04, 2007 at 03:40:58AM -0500, Ryan Schmidt wrote:
>> I guess I don't understand why dir2 depends on dir1 since both are
>> subdirectories of /. It's not /dir1/dir2: it's /dir1; /dir2.
> Of course dir2 does not depend on dir1 in this scenario.
> If you had asked Subversion to check out only dir2, la...
> svn co file://$(pwd)/test-repo/dir2
> ...it would have succeeded. That's what Erik is trying to say when he says
> "if a damaged revision is not required to construct a later revision, it's


> simply skipped and no damage will be detected." If the revision creating
> dir1 is corrupted, but you only ask to check out the unrelated dir2, then
> no error is reported and it works fine.
> But that's not what you asked. You asked Subversion to verify all
> revisions. And it reported an error in revision 1. Which is correct,
> because revision 1 was corrupted.

And it stopped there, even though I asked it to verify all revisions.

svnadmin dump also stops there, and I believe this was the original
complaint. The OP asked if there was a way for svnadmin verify to mark
that revision as bad, skip it and let svnadmin dump dump the rest. It
would be a waste if all the other 150k revisions didn't depend on this
one and just because of this couldn't be dumped.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 4 14:18:07 2007

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.