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

Re: Subversion DB corruption

From: <kfogel_at_collab.net>
Date: 2004-09-13 03:46:01 CEST

Mike Scott <mike@mikescommunity.com> writes:
> The machine hung, it wasn't a disk problem. I don't believe there was
> any hardware level corruption. If the journal files were corrupted,
> I'm curious how that happened. I'd like to know if there's a scenario
> whereby aborting in the middle of a write (e.g. by the processor
> overheating and just stopping running code, which I also suspect is
> what happened here) could cause corruption. Is it possible to rule
> that out? If not, then perhaps there's a weakness in the system that
> needs to be addressed.

I agree with you that the likeliest explanation is a weakness in the
software -- after all, an aborted write ought not harm data that was
already written. I'm not sure how to start looking for the weakness,
though :-(. I don't believe we've seen this behavior before, and a
reproduction recipe that involves overheating the processor is going
to be a bit impractical... :-)

(Not trying to be defeatist, just not sure what the next step is.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 13 05:31:29 2004

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.