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

Re: corrupted text-base files not being detected and/or repaired

From: Bhuvaneswaran Arumugam <bhuvan_at_collab.net>
Date: 2007-06-18 16:43:53 CEST

On Mon, 2007-06-18 at 14:16 +0200, Erik Huelsmann wrote:
> On 6/18/07, Bhuvaneswaran Arumugam <bhuvan@collab.net> wrote:
> > On Mon, 2007-06-18 at 06:18 -0500, Ben Collins-Sussman wrote:
> > > On 6/18/07, Richard Carlsson <richard.carlsson@iar.se> wrote:
> > >
> >
> > > What you're describing isn't a corruption in the text-base file
> > > itself, but a corruption of the .svn/entries metadata. I don't even
> >
> > I think it could be vice-versa as well, either the entries file is
> > corrupted or, the text-base file is corrupted. If I'm right, the
> > checksum algorithm we use must detect both of these cases.
> No, not really: updating a file which doesn't have changes in the
> repository doesn't read either the file or its text-base. For
> performance reasons, that's correct.
> What we may want to offer though is a 'svn cleanup --force' or 'svn
> cleanup --integral' to check all text-bases regardless of the time it
> may take to do the checks required.

OK. I assume you meant that we can check the checksum of text-base file
with checksum stored in entries file. Probably, if they do not match, we
can copy the versioned file to the text-base, hence, both the checksums
may match.


Received on Mon Jun 18 16:43:54 2007

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.