7091@xxxxxxxxxx wrote: > Tejun Heo writes: >> Sounds awfully similar to the recent nvidia data corruption issue. It >> was involving the IOMMU and one of the workarounds was not using IOMMU, >> IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU >> off by passing "iommu=off" as kernel parameter. >> -- >> tejun > > Blast. I stand corrected - it didn't fix it. > I now have 3 300G drives hanging off the add-in card, sda sdb sdc. I > did the following: > # Make a RAID5 array of 3 out of the 4 drives I'll eventually be using > mdadm --create /dev/md6 --chunk=64 --level=raid5 --raid-devices=4 > /dev/sda1 /dev/sdb1 /dev/sdc1 missing > # Make the FS > mkfs.ext3 /dev/md6 > # Test > cp KNOPPIX_V5.1.0CD-2006-12-30-EN.iso kn1.iso > cp kn1.iso kn2.iso > cp kn2.iso kn3.iso > cp kn3.iso kn4.iso > # Check > md5sum *.iso > eea5ecb53f1c6a397bcfeedc2fd42c64 kn1.iso > 0360941210aa2d7159999e37c636f8cb kn2.iso > md5sum: kn3.iso: Input/output error > 86b008915fe02569a513b6c5ec45a523 kn4.iso > In the dmesg: > [ 2619.483783] attempt to access beyond end of device > [ 2619.483956] md6: rw=0, want=25890291976, limit=1758201216 Something went very wrong here and it probably doesn't have much to do with IOMMU corruption. Care to post full dmesg? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
