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.
Cheers,
Mike.
kfogel@collab.net wrote:
>Mike Scott <mike@mikescommunity.com> writes:
>
>
>>The machine hung just after committing, so my guess is that there was
>>still unflushed data in the disk cache. I would have expected a
>>journalling system to ensure that it's journal update were flushed to
>>disk before making any changes to the data.
>>
>>
>
>I think what Max means is that something may have corrupted existing
>journal files. For example, no journaling file system (no matter how
>good) can recover from having its journal files themselves corrupted
>by a skipping disk head.
>
>(Obviously, we don't know exactly what happened with your machine, so
>it's hard to determine the likelihood that old data got blown away.)
>
>
>
>
Received on Sun Sep 12 02:46:00 2004