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

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

From: Markus Karg <markus.karg_at_quipsy.de>
Date: 2005-10-07 16:22:55 CEST

thank you for clarification on what the SVN team actually thinks about this, because in the previous discussion this was unclear. It's good to see that the team has understood that there are users very concerned even on corrupted properties and we don't think that it is only hypothetical.
Thanks for SVN, it's a great tool.
All what we want is to make it even better.
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D


Von: Daniel Berlin [mailto:dberlin@dberlin.org]
Gesendet: Fr 07.10.2005 13:57
An: Markus Karg
Cc: kfogel@collab.net; Leon Zandman; users@subversion.tigris.org
Betreff: Re: AW: Re: AW: AW: AW: How to check integrity of database?

On Fri, 2005-10-07 at 09:27 +0200, Markus Karg wrote:
> 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? :-(

Except that svnadmin is by definition, such a tool, since it verifies
everything that is checksummed.

> This whole discussion proofs that I am not the only one that is
> concerned about corrupted repositories (including properties),

Again, these are revision properties.

> so I don't understand that the SVN development team is more or less
> laughing at this task. :-((

What are you talking about? Nobody is laughing at anyone.

Karl is clearly attempting to discover the reasons users want this, and
what they are looking for, in order to determine whether we should do
something about this.

We don't implement things in subversion willy nilly.
We certainly can't design a feature without knowing why users want it,
what it is supposed to do, etc.

You have to realize that, AFAIK, svnadmin verify was originally
implemented to catch cases *we* broke the repository, through storing
the wrong data, or the clients transmitting the wrong data.
The clients have been the main verification point thus far, not svnadmin

If svnadmin verify is going to be extended to verify things other than
versioned data, we certainly need to know what cases of corruption we
are going to try to be verifying, who will be doing the verifying, etc.

We don't design subversion to work in a theoretical world, we design it
to work in the real world. Hence, Karl is also trying to find out if
the corruption you are trying to prevent has *ever* happened in the real
world, or is even *likely* to happen.
Received on Fri Oct 7 16:27:57 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.