Re: Again - inode races [PATCH] Re: Corrupted inode list?

Steven L Baur (steve@miranova.com)
30 Jan 1997 16:04:14 -0800


Stephen C Tweedie writes:

> Hi,
> On Tue, 21 Jan 1997 00:15:30 -0500 (EST), Benjamin C R LaHaise
> <blah@dot.superaje.com> said:

...
>> finished, plus any block writes and.... ick! This should even fix
>> the problems some people were having with disk quotas not being
>> properly updated (the drop in clear_inode).

...
> However, having said all that, we've been bitten by races in this part
> of the code before, so if you _can_ demonstrate a real race condition
> in the VFS itself, please do let me know...

I don't know how I can demonstrate a problem, but something is
definitely still amiss. I just got bitten by this bug again a few
hours ago after eight days of using the patch in this thread and
2.0.28:

Jan 30 13:04:06 altair kernel: EXT2-fs warning (device 16:02): ext2_free_inode: bit already cleared for inode 286988
Jan 30 13:04:06 altair last message repeated 2 times

The total lossage this time was zeroed inodes 286,985 through 286,988
and 364,586 through 364,588. :-(

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.