I have also experienced file system corruption with 2.2.4. The problem most
likely lies in the /fs/buffer.c file which the raid patch had a conflict
with.
<>< Lance.
Tony Wildish wrote:
> 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....
>
> 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.
