From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-raid@vger.kernel.org
Subject: checking state of RAID (for automated notifications)
Date: Wed, 06 Sep 2006 10:44:24 +0200 [thread overview]
Message-ID: <44FE8A68.8060306@wpkg.org> (raw)
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?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2006-09-06 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 8:44 Tomasz Chmielewski [this message]
2006-09-06 16:50 ` checking state of RAID (for automated notifications) Mike Hardy
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=44FE8A68.8060306@wpkg.org \
--to=mangoo@wpkg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.