On Fri, Jun 29, 2007 at 04:07:51PM -0300, Andreas Hasenack wrote:
> On Fri, Jun 29, 2007 at 02:52:04PM -0400, Jing Xue wrote:
> >
> > Sorry if I'm missing something very obvious here, but assuming a backup
> > implementation that ensures timely and completely verified backups, why
> > would one insist on repairing the repository? AFAIK, a hotcopy backup is a
> > good-to-go repository itself.
>
> Following this rationale, you could as well as toss all your /sbin/fsck*
> files. :)
The essential value of fsck to me is that, in the event of a corruption,
it allows me a much better chance (by trying to repair as much as
possible) to get to a point where I can comfortably examine the damage,
and decide whether I'd like to restore a backup and actually do it.
Without fsck, I might be very well shut out of my system due to even the
least amount of corruption.
Such is not the case in svn. It's extremely easy to restore a repository
from a backup. I would bother to try to rely on either a program's or my
guess work to repair the repository only in one case, that is some one
checked in something after the last backup, and nobody else updated
their work copies since then, _and_ the guy lost his own copy as well.
Does that happen? Sure. Often enough to warrant a repair tool? I don't
know. 8-)
--
Jing Xue
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 30 05:35:41 2007