On Tue, Oct 11, 2011 at 04:13:38PM +0200, Anders Ossowicki wrote: > On Tue, Oct 11, 2011 at 03:34:48PM +0200, Christoph Hellwig wrote: > > This is core VM code, and operates purely on on-stack variables except > > for the page cache radix tree nodes / pages. So this either could be a > > core VM bug that no one has noticed yet, or memory corruption. Can you > > run memtest86 on the box? > > Unfortunately not, as it is a production server. Pulling it out to memtest 256G > properly would take too long. But it seems unlikely to me that it should be > memory corruption. The machine has been running with the same (ecc) memory for > more than a year and neither the service processor nor the kernel (according to > dmesg) has caught anything before this. It would be a rare (though I admit not > impossible) coincidence if we got catastrophic, undetected memory corruption a > week after attaching a new raid controller with a new disk array. Memory corruption can be caused by more than just a bad memory stick. You've got a brand new driver running your brand new controller and it may still have bugs - it might be scribbling over memory it doesn't own because of off-by-one index errors, etc. It's much more likely that that new hardware or driver code is the cause of your problem than an undetected ECC memory error or core VM problem. FWIW, if it's a repeatable problem, you might want to update the driver and controller firmware to something more recent and see if that solves the problem.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
