Re: [PATCH] Issue #1074: Need a svnadmin command to verify that the repository is not corrupted (Take 2)

On Wednesday 06 August 2003 00:48, cmpilato@collab.net wrote:
> John Szakmeister <john@szakmeister.net> writes:
> > Perhaps the best thing to do is recommend that people run 'svnadmin dump'
> > every once in a while to make sure nothing has been corrupted.
>
> Ooh! Here's a thought. What if we added a --dry-run option to
> 'svnadmin dump'? That way at least folks don't pay the cost of the
> output I/O. Basically, this option would cause the "stream" passed to
> svn_repos_dump to be NULL, and we'd just check for non-NULL before
> each call to svn_stream_printf() and svn_stream_write() in
> libsvn_repos/dump.c. Note that we'd still do the *read* of the
> file/directory data, so we get the checksum verification. Also, we
> still pass a valid "feedback_stream" to the function, so we can see
> progress and warnings.

Hehe, I was actually going to mention something like that but I thought I'd
better check and make sure that feature wasn't already there. :-)

Yes, I think that is a better way to go... and it's something that I'd use.
:-) Should I take a stab at doing this?

-John

PS I'll be out for the following 4 days so it'll be a little bit before I get
started.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 6 11:25:50 2003