linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <r.scobie@clear.net.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Assembly failure
Date: Sat, 14 Jul 2012 08:34:40 +1200	[thread overview]
Message-ID: <50008660.7020905@clear.net.nz> (raw)

Brian Candler wrote:

------------------------------------

One final point. I would like to be able to monitor for suspect or failed
drives.  Is my best bet to look at /proc/mdstat output and identify drives
which have been kicked out of the array?  Or to monitor SMART variables (in
that case though I need to decide which ones are the most important to
monitor, and what thresholds to set)?

-------------------------------------------

For years I have used smartd without issues and it will log and email 
anomalies as they occur.

It is also advisable to regularly "scrub" all md devices, to flush out 
faulty sectors:

echo check > /sys/block/mdX/md/sync_action

See Documentation/md.txt for details.

Regards,

Richard

             reply	other threads:[~2012-07-13 20:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 20:34 Richard Scobie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-10 16:33 Assembly failure Brian Candler
2012-07-10 16:48 ` Sebastian Riemer
2012-07-10 17:06   ` Brian Candler
2012-07-10 17:38     ` Sebastian Riemer
2012-07-10 18:59       ` Brian Candler
2012-07-11  2:43         ` NeilBrown
2012-07-11  7:58           ` Brian Candler
2012-07-11  8:27             ` Christian Balzer
2012-07-11  9:09               ` Brian Candler
2012-07-11 10:32                 ` Mikael Abrahamsson
2012-07-11 10:47                   ` Brian Candler
2012-07-11 10:44               ` Roman Mamedov
2012-07-11 17:21                 ` Christian Balzer
2012-07-13 18:52               ` Brian Candler
2012-07-10 17:05 ` pants

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=50008660.7020905@clear.net.nz \
    --to=r.scobie@clear.net.nz \
    --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).