Mark Lord wrote (ao):...Sander wrote:Mark Lord wrote (ao):...On Friday 17 February 2006 03:45, Jeff Garzik wrote:Submit a patch...You mean, something like this one?[ 633.449961] md: md1: sync done....
[ 633.456070] RAID5 conf printout:
[ 633.456117] --- rd:9 wd:9 fd:0
[ 1872.338185] ata6: translated op=0x2a ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 1872.338239] ata6: status=0xd0 { Busy }
[ 5749.285084] ata8: translated op=0x2a ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 5749.285138] ata8: status=0xd0 { Busy }
[ 5906.008461] ata6: translated op=0x2a ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
[ 5906.008515] ata6: status=0xd0 { Busy }
...SCSI opcode 0x2a is WRITE_10, so the errors are being reported
in response to the writes to bigfile.$i.
I am using the sata_mv driver, which is beta. That might explain why it
behaves not totally as expected in your eyes. I have no clue anyway :-)