On Sun, 26 Feb 2006, Andre Noll wrote: > > Are there any workarounds? It seems odd that raid1 would be the only > > thing that has a problem. > > You could add your drive to the blacklist just to see if that makes any > difference.
Unfortunately, it didn't make any difference. After adding in the drive IDs, they're identified correctly: ata1(0): applying Seagate errata fix ata2(0): applying Seagate errata fix but I still get the corruption on md1 (sda1 + sdb1 in raid 1) but not on either sda1 or sdb1 when the raid is shut down and the partitions are used individually. As a new test I made two raid1s, sda1+sda2 and sdb1+sdb2, and did the same tests with both of them at once and there was no corruption. Moses - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
