Hello,
David Shaw wrote:
> I'm having a problem with data corruption using devmapper on a SATA
> disk using sata_sil24. I've done some work tracking it down, and
> hopefully you folks can point me further in the right direction.
>
> The kernel I'm using is 2.6.21-1.3228.fc7 (i.e. Fedora 7). LVM2 is
> lvm2-2.02.24-1.fc7. The dmsetup and libdevmapper is
> device-mapper-1.02.17-7.fc7.
>
> The original setup that showed the problem is this:
>
> Starting with two 500GB SATA drives (interface card uses a Silicon
> 3124 chipset), /dev/sdd and /dev/sde. I partitioned each into two
> 250GB chunks (250*1000*1000*1000, not 250*1024*1024*1024), and set up
> two RAID 1 sets such that /dev/md0 is /dev/sdd1+/dev/sde1 and /dev/md2
> is /dev/sdd2+/dev/sde2. I then created a volume group ("storage") on
> top of /dev/md0 and /dev/md1. Finally, I allocated two logical
> volumes on top of that: "one" is -L300GB and "two" is -L100GB.
-ETOOMANYCOMPNONETS. If it's data corruption with sata_sil24, it's
highly likely that you're gonna be able to regenerate the problem
without using raw /dev/sdd and /dev/sde devices. Please try that.
> Note that this simplified reproduction case uses only the device
> mapper: RAID is not involved, nor is LVM. "dmsetup table" says:
>
> two: 0 209715200 linear 8:32 482345000
> one: 0 482344960 linear 8:32 0
Can you try this on another controller so that we can tell whether the
problem lies with dm or ata?
--
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
