- To: linux-raid@xxxxxxxxxxxxxxx
- Subject: tracking parity mismatches to a failing disk
- From: Michael Peterson <Michael.Peterson@xxxxxxxx>
- Date: Wed, 09 May 2012 15:16:08 -0400
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
I'm trying to identify the source of a non-zero mismatch_cnt on a
six-disk RAID6 md array. I think I've identified it as /dev/sdf since
that is the only device with a non-zero value in
/sys/block/md0/md/dev-sd*/errors. Is that the right way to track parity
mismatches back to a disk?
OS is CentOS 5.8 -> mdadm 2.6.9
Thanks,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ATA RAID]
[Linux SCSI Target Infrastructure]
[Managing RAID on Linux]
[Linux IDE]
[Linux SCSI]
[Linux Hams]
[Device-Mapper]
[Kernel]
[Linux Books]
[Linux Admin]
[Linux Net]
[GFS]
[RPM]
[git]
[Photos]
[Yosemite Photos]
[Yosemite News]
[AMD 64]
[Linux Networking]