linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: tbayly@bluehost.com
Cc: Brassow Jonathan <jbrassow@redhat.com>,
	"linux-raid@vger.kernel.org Raid" <linux-raid@vger.kernel.org>
Subject: Re: Periodically scanning RAID arrays for inconsistencies
Date: Sat, 02 Mar 2013 11:24:37 -0500	[thread overview]
Message-ID: <513227C5.3010400@turmel.org> (raw)
In-Reply-To: <1362175859.18278.76.camel@148>

On 03/01/2013 05:10 PM, Tregaron Bayly wrote:
> 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.

In general, this is called "scrubbing" your array, and it is *vital* to
do this on a regular basis.  Weekly is good.  You should only use
"check" to find mismatches (and it will fix UREs).  If any mismatches
are found, use "repair" to synchronize the devices, then fsck to fix any
resulting errors.

There's lots of history on this in the archives...

Phil


  reply	other threads:[~2013-03-02 16:24 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 [this message]
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=513227C5.3010400@turmel.org \
    --to=philip@turmel.org \
    --cc=jbrassow@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=tbayly@bluehost.com \
    /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).