I have had problems with 2.5.10 (first few blocks of the root
filesystem overwritten) and then went back to 2.5.8 that I had
used for a while already, but then also noticed corruption there.
Back at 2.4.17 today..
In my case the problem was almost certainly the IDE code.
More in particular, the 2.5.8 corruption happened on four
different occasions, on two different disks, hanging off
an HPT366 that is without problems on 2.4*. Three of the
four times there were messages like
Apr 29 15:26:00 kernel: hde: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 29 15:26:00 kernel: hde: task_out_intr: error=0x04 { DriveStatusError }
May 2 01:21:23 kernel: hdf: status error: status=0x50 { DriveReady SeekComplete }
May 2 01:21:23 kernel: hdf: no DRQ after issuing WRITE
May 2 01:21:37 kernel: hdf: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
May 2 01:21:37 kernel: hdf: task_out_intr: error=0x04 { DriveStatusError }
Each time some data was written at a wrong address on disk.
Now these are ext2 filesystems, so I noticed.
Elsewhere I have ext3 and reiserfs, but journalling does not
protect against IDE drivers that write stuff to the wrong disk block.
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/