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

AW: Re: AW: AW: AW: How to check integrity of database?

From: Markus Karg <markus.karg_at_quipsy.de>
Date: 2005-10-07 09:27:34 CEST

So we shall wait for the day our data is corrupt to make you understand that we (the SVN admins) like to have one single tool that guarantees that it did the best it could to to tell us whether the FSFS repository is corrupted or not? :-(
This whole discussion proofs that I am not the only one that is concerned about corrupted repositories (including properties), so I don't understand that the SVN development team is more or less laughing at this task. :-((
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D


Von: kfogel@newton.ch.collab.net im Auftrag von kfogel@collab.net
Gesendet: Do 06.10.2005 20:07
An: Leon Zandman
Cc: Daniel Berlin; users@subversion.tigris.org
Betreff: Re: AW: AW: AW: How to check integrity of database?

Leon Zandman <lzandman@lode.nl> writes:
> > We don't bother to checksum them, because they are
> > unversioned, and you shouldn't be storing anything critical
> > in there anyway.
> I don't understand why you don't checksum the properties. I do
> understand why the properties/log messages aren't versioned, but I'd
> still like to know when my repository has been corrupted somehow.

I think it's because we just didn't think of it.

We could checksum them, I suppose. But so far there hasn't been a
real-world instance of them being corrupted (yet no other part of the
repository being corrupted), so we haven't bothered. Unless there's
been a recent report of such and I just missed it? Let us know if so.

How's that for a direct answer? :-)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 7 09:31:39 2005

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.