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

Re: Safe to backup if failed svnadmin verify?

From: Mark Clements <gmane_at_kennel17.co.uk>
Date: 2007-04-27 17:13:17 CEST

"Johnathan Gifford" <jgifford@wernervas.com> wrote in message
>> * Running "svnadmin hotcopy" or "svnadmin dump" on a repository that
>> "svnadmin verify" will not cause any damage to the repository, or modify
>> in any way.
> Correct
>> * "svnadmin hotcopy" will succeed, and the resulting backup will be an
>> copy of the repo, including the errors.
> Yes
>> * "svnadmin dump" will fail when it hits the bad revision (resulting in,
>> what? an incomplete dump file, no dump file, a full dump with bad
>> omitted or full dump which is corrupt/unusable?)
> If you are iterating over the repository and dumpingt each revision
> incrementally, only that revision will fail. If you are dump the entire
> repository from revision 1 to X then the dump will fail when it encounters
> the bad revision. If you dump from revision X (loosing all history of
> this will not fail unless X is the corrupt revision.
> I don not think you can get an incomplete dump or a full dump with bad

OK - just tested this last point, by creating a repo with 5 revisions (0 to
4) and corrupting rev 2. The dump file terminates after outputting the
revision properties, but before outputting any actual data from that

Basically, what happens is that, when the error occurs, an error message
goes to stderr and the dump process terminates, so whatever is written up to
that point is retained. As you say, an incremental or partial dump that
doesn't include any bad revisions will work fine.

Thanks for all your help,

- Mark Clements

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 27 17:14:31 2007

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