2 messages, 2 authors, 2012-06-04 · open the first message on its own page
From: Michael Peterson <hidden>
Date: 2012-05-09 19:16:08
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
From: NeilBrown <hidden>
Date: 2012-06-04 04:17:04
On Wed, 09 May 2012 15:16:08 -0400 Michael Peterson [off-list ref] wrote:
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
There is a program in the mdadm source distro called "raid6check" which can possibly help you. NeilBrown