Hi,
On Mon, 29 Mar 1999 11:28:25 +0100, Richard Jones
<[EMAIL PROTECTED]> said:
> Not so fast there :-)
> In the stress tests, I've encountered almost silent
> filesystem corruption. The filesystem reports errors
> as attached below, but the file operations continue
> without error, corrupting files in the process. At
> no time did the RAID software report any problem, nor
> did any reconstruction kick in.
> Anyone have any ideas what might be going on? It doesn't
> seem to be exclusively a 2.2.4 thing. I've seen similar
> problems with 2.0.36-19990128.
This is a pretty good indication of a hardware fault. Looking at the
messages:
> Mar 26 20:52:35 fred kernel: EXT2-fs error (device md(9,0)): ext2_free_blocks:
>Freeing blocks not in datazone - block = 550046767, count = 1
> Mar 26 20:52:36 fred kernel: EXT2-fs error (device md(9,0)): ext2_free_blocks:
>Freeing blocks not in datazone - block = 536870912, count = 1
> Mar 27 10:47:59 fred kernel: EXT2-fs error (device md(9,0)):
> ext2_free_blocks: Freeing blocks not in datazone - block = 538609421,
> count = 1
these are block numbers (in hex): 20C90C2F, 20000000, 201A870D.
Something is randomly flipping bit 29 in the block addresses (the block
numbers are entirely valid apart from this). This may be a disk or
controller fault, but I'd replace the cabling first.
--Stephen
