linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: checking state of RAID (for automated notifications)
Date: Wed, 06 Sep 2006 09:50:13 -0700	[thread overview]
Message-ID: <44FEFC45.1080500@h3c.com> (raw)
In-Reply-To: <44FE8A68.8060306@wpkg.org>


<berlin> % rpm -qf /usr/lib/nagios/plugins/contrib/check_linux_raid.pl
nagios-plugins-1.4.1-1.2.fc4.rf

It is built in to my nagios plugins package at least, and works great.

-Mike

Tomasz Chmielewski wrote:
> I would like to have RAID status monitored by nagios.
> 
> This sounds like a simple script, but I'm not sure what approach is
> correct.
> 
> 
> Considering, that the "health" status of /proc/mdstat looks like this:
> 
> # cat /proc/mdstat
> Personalities : [raid1] [raid10]
> md2 : active raid10 sda2[4] sdd2[3] sdc2[2] sdb2[1]
>       779264640 blocks super 1.0 64K chunks 2 near-copies [4/4] [UUUU]
> 
> md1 : active raid1 sdd1[1] sdc1[0]
>       1076224 blocks [2/2] [UU]
> 
> md0 : active raid1 sdb1[1] sda1[0]
>       1076224 blocks [2/2] [UU]
> 
> unused devices: <none>
> 
> 
> What my script should be checking?
> 
> Does the number of "U" (8 for this host) letters indicate that RAID is
> healthy?
> Or should I count "in_sync" in "cat /sys/block/md*/md/rd*/state"?
> Perhaps the two approaches are the same, though.
> 
> 
> What's the best way to determine that the RAID is running fine?
> 
> 

  reply	other threads:[~2006-09-06 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06  8:44 checking state of RAID (for automated notifications) Tomasz Chmielewski
2006-09-06 16:50 ` Mike Hardy [this message]
2006-09-07  8:30   ` Tomasz Chmielewski

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=44FEFC45.1080500@h3c.com \
    --to=mhardy@h3c.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mangoo@wpkg.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).