From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Nagios probe for btrfs RAID status?
Date: Fri, 22 Nov 2013 17:52:35 +0000 (UTC) [thread overview]
Message-ID: <pan$aedd2$55675d23$87b751ab$aaf09e6d@cox.net> (raw)
In-Reply-To: 528F6085.4020603@pocock.com.au
Daniel Pocock posted on Fri, 22 Nov 2013 14:47:49 +0100 as excerpted:
> I just did a search and couldn't find any probe for btrfs RAID status
>
> The "check_raid" plugin seems to recognise mdadm and various other types
> of RAID but not btrfs
>
> Has anybody seen a plugin for Nagios or could anybody comment on how it
> should work if somebody wants to make one?
>
> For example, would the command
>
> btrfs filesystem show --all-devices
>
> give a non-zero error status or some other clue if any of the devices
> are at risk?
[btrfs personal user/sysadmin, not a dev, not anything large enough to
have personal nagios experience...]
AFAIK, btrfs raid modes currently switch the filesystem to read-only on
any device-drop error. That has been deemed the simplest/safest policy
during development, tho at some point as stable approaches the behavior
could theoretically be made optional.
So detection could watch for read-only and act accordingly, either
switching back to read-write or rebooting or simply logging the event, as
deemed appropriate.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-11-22 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 13:47 Nagios probe for btrfs RAID status? Daniel Pocock
2013-11-22 17:52 ` Duncan [this message]
2013-11-23 3:59 ` Anand Jain
2013-11-23 8:37 ` Daniel Pocock
2013-11-23 9:20 ` Daniel Pocock
2013-11-23 10:35 ` Duncan
2013-11-23 11:44 ` Daniel Pocock
2013-11-23 16:32 ` Duncan
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='pan$aedd2$55675d23$87b751ab$aaf09e6d@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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.