From: NeilBrown <neilb@suse.de>
To: Michael Peterson <Michael.Peterson@duke.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: tracking parity mismatches to a failing disk
Date: Mon, 4 Jun 2012 14:17:04 +1000 [thread overview]
Message-ID: <20120604141704.12dcbd3e@notabene.brown> (raw)
In-Reply-To: <4FAAC278.6080303@duke.edu>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Wed, 09 May 2012 15:16:08 -0400 Michael Peterson
<Michael.Peterson@duke.edu> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-06-04 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 19:16 tracking parity mismatches to a failing disk Michael Peterson
2012-06-04 4:17 ` NeilBrown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120604141704.12dcbd3e@notabene.brown \
--to=neilb@suse.de \
--cc=Michael.Peterson@duke.edu \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).