From: NeilBrown <neilb@suse.de>
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: Mon, 4 Mar 2013 16:42:21 +1100 [thread overview]
Message-ID: <20130304164221.70d51311@notabene.brown> (raw)
In-Reply-To: <81526C3C-7F95-4A17-B91B-8FD45BED55DE@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Fri, 1 Mar 2013 15:50:05 -0600 Brassow Jonathan <jbrassow@redhat.com>
wrote:
> Is there a way to periodically scan a RAID array to report any discrepancies? This would be something like the initial synchronization, but would do nothing but report anomalies. For example, it is possible for tracks to be altered when adjacent tracks are repeatedly written. It might happen rarely, but without a periodic scan, you would never know about it. Leaving aside the question of /what/ to do when an anomaly is found, I haven't seen any code or indication in the man page for 'mdadm' that would suggest this is currently possible. Am I wrong? Is there a way to do this?
>
> brassow
echo check > /sys/block/mdX/md/sync_action
look for results in /sys/block/mdX/md/mismatch_cnt
See "SCRUBBING AND MISMATCHES" in "man 4 md".
Yes it would be nice if mdadm provided a nicer interface to this. Patches
welcome:-)
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-03-04 5:42 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
2013-03-02 16:24 ` Phil Turmel
2013-03-04 5:42 ` 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=20130304164221.70d51311@notabene.brown \
--to=neilb@suse.de \
--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).