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

Re: [Issue 3596] 'hotcopy' of packed fsfs repos may corrupt target revprops.db

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 14 Apr 2010 09:30:37 +0100

"Hyrum K. Wright" <hyrum_wright_at_mail.utexas.edu> writes:

> On Tue, Apr 13, 2010 at 7:08 AM, Philip Martin <philip_at_codematters.co.uk>wrote:
>> > The rep sharing cache is just a cache, and can be truncated or
>> > deleted without impact on the correctness of the system.
>> That's a way to fix a corrupt hotcopy but I don't think it prevents
>> the corruption.
> What kind of corruption are we talking about? The file gets corrupted and
> isn't recognized by SQLite as a valid database? It sees the file is a valid
> database, but doesn't contain some rows? The data contained in the SQLite
> data is wrong?

I think there is another problem in 1.6: the rep cache is one of the
last things copied and so it could be newer than the rev files that
got copied, which means it could refer to a rep that didn't get
copied. A little experimentation shows that such a hotcopy will
verify successfully, however a subsequent commit that uses the missing
rep (which will succeed) produces a corrupt repository.

I think we can avoid this by copying the rep cache before the rev

Received on 2010-04-14 10:31:13 CEST

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