tracking parity mismatches to a failing disk

Started by Michael Peterson on May 9, 2012 · 2 messages from 2 authors · Last reply Jun 4, 2012

open the first message on its own page

Message details and related content
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
Message details and related content
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
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help