Hello,
this sound to me like bad memory. I had a very similar problem recently
and it was a bad SIMM. I was lucky enough to have four SIMMS in the
machine so I can still run with only two, having removed the bad SIMM and
its partner.
Two suggestions:
Try booting with the 'mem=xxxM' option to limit yourself to a small
amount of RAM. If you are lucky then the problem is high enough in the
memory that you can limit yourself to a good region and it will work.
Try breaking your RAID and putting a normal ext2 filesystem on those
partitions and repeating your tests (using all the RAM you have). This
will show if the problem is in the RAID software or not. I would be
_very_ interested to hear if this acquits the RAID software!
I have been running 2.0.36 + 0145-19990309 on a P133 and a 386 for a
while now. Since I fixed my memory problem it has worked fine everywhere.
I have been running my own stress-tests (if you want to take a look at my
scripts see http://atddoc.cern.ch/~wildish/) and have seen no errors in
several days of tests.
Cheers,
Tony.
On Mon, 29 Mar 1999, Richard Jones wrote:
> 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.
