From: Tregaron Bayly <tbayly@bluehost.com>
To: Brassow Jonathan <jbrassow@redhat.com>
Cc: "linux-raid@vger.kernel.org Raid" <linux-raid@vger.kernel.org>
Subject: Re: Periodically scanning RAID arrays for inconsistencies
Date: Fri, 01 Mar 2013 15:10:59 -0700 [thread overview]
Message-ID: <1362175859.18278.76.camel@148> (raw)
In-Reply-To: <81526C3C-7F95-4A17-B91B-8FD45BED55DE@redhat.com>
On Fri, 2013-03-01 at 15:50 -0600, Brassow Jonathan wrote:
> Is there a way to periodically scan a RAID array to report any discrepancies?
Yes, it's possible - Redhat distributes a script called raid-check that
is a good example of this very thing.
Documentation/md.txt talks about 'check' and 'repair' as valid words for
sync_action in sysfs. The number of errors found will be reported to
mismatch_cnt. These can be found at /sys/block/md#/md for your array.
hth,
Tregaron
next prev parent reply other threads:[~2013-03-01 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 21:50 Periodically scanning RAID arrays for inconsistencies Brassow Jonathan
2013-03-01 22:10 ` Tregaron Bayly [this message]
2013-03-02 16:24 ` Phil Turmel
2013-03-04 5:42 ` NeilBrown
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=1362175859.18278.76.camel@148 \
--to=tbayly@bluehost.com \
--cc=jbrassow@redhat.com \
--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).