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

Re: "svnadmin verify" dangerously broken

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-08-06 16:45:58 CEST

On Fri, 2004-08-06 at 10:20, Branko ÄŒibej wrote:
> Another way to fix this without propagating the NULL-stream exception
> all the way down to the streams API would be to actually create a
> /dev/null-like stream with a no-op writer function, and use that in
> "svnadmin verify" instead.

I like that better; I always thought the NULL exceptions in
svn_repos_dump were stupid, and NULL exceptions in the svn_stream API
would be even moreso.

I don't know how to make "svn verify" check that the repository won't
break in the future on account of current corruption. We can advise
people to run "svn verify" on the result of a hot-backup (which always
gets DB recovery, I think) rather than the source, but that's all I
know.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 6 16:46:58 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.