> There is a data corruption problem too, for reading and writing.
>
> I am getting data corruption some time after the DMA error happens if I
> have to reboot the machine (for other reasons like X crashing and sysrq
> not working).
>
> It's not the normal "I rebooted and have a few inconsistencies". fsck
> complains about runs of contiguous inodes having mode 0177777, which
> sometimes are actual files whose contents are lost. Sometimes fsck core
> dumps (oh well).
Get e2fsprogs-1.18, some crashes on badly mangled inodes have been fixed.
> I imagine all-ones blocks are being written.
I saw massive filesystem corruptions (random garbage written over inodes,
AFAIKS) on this machine (P2, RedHat 6.1) for a long time, from 2.3.20
(first 2.3.x I tried here) up to something like 2.3.34 or so. Later kernels
have been working fine.
-- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Viņa del Mar, Chile +56 32 672616- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/