[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: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-07-04 16:06:43 CEST

On 7/4/07, Andreas Hasenack <andreas@mandriva.com.br> wrote:

[ ... ]

> > 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.

You basically asked it: "Is the repository in good condition?" And it
answered "Sorry, no." And annotated that with "Because your revision 1
is broken."

> svnadmin dump also stops there, and I believe this was the original
> complaint.

Well that's a good thing :-) They're implemented using exactly the same code!

> 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.

Ah! But this isn't true: you can dump them, but not with a single command...

As I'm on holidays, I can't verify it myself, but I've been told that
the trunk (1.5-dev) version of svnadmin verify supports
revision(range)s, so that this functionality is essentially available
with that version (all be it not with 1 Subversion command).



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 4 16:06:46 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.