From: Anand Jain <anand.jain@oracle.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
linux-btrfs@vger.kernel.org
Subject: Re: How to detect / notify when a raid drive fails?
Date: Mon, 30 Nov 2015 22:01:26 +0800 [thread overview]
Message-ID: <565C56B6.7010106@oracle.com> (raw)
In-Reply-To: <1448644747.11377.45.camel@scientia.net>
On 11/28/2015 01:19 AM, Christoph Anton Mitterer wrote:
> On Fri, 2015-11-27 at 17:16 +0800, Anand Jain wrote:
>> I understand as a user, a full md/lvm set of features are important
>> to begin operations using btrfs and we don't have it yet. I have to
>> blame it on the priority list.
> What's would be especially nice from the admin side, would be something
> like /proc/mdstat, which centrally gives information about the health
> of your RAID.
Yep. Its planned. A design doc was in my draft for some time now, I
just sent it to the mailing list for review comments.
> It can/should of course be more than just "OK" / "not OK"...
> information about which devices are in which state, whether a
> rebuild/reconstruction/scrub is going on, etc. pp.
right.
> Maybe even details of properties like chunk sizes (as far as these
> apply to btrfs).
>
> Having a dedicated monitoring process... well nice to have, but
> something like mdstat is, always there, doesn't need special userland
> tools and can easily used by 3rd party stuff like Icinga/Nagios
> check_raid.
yep. will consider.
> I think the keywords here are human readable + parseable... so maybe
> even two files.
yeah. for parseable reasons I liked procs, there is experimental
/proc/fs/btrfs/devlist. but procs is kind of not recommended. So
probably we would need a wrapper tool on top the sysfs to provide
the same effect.
Thanks, Anand
>
> Cheers,
> Chris.
>
prev parent reply other threads:[~2015-11-30 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 5:14 How to detect / notify when a raid drive fails? Ian Kelling
2015-11-27 5:30 ` Duncan
2015-11-27 7:42 ` Ian Kelling
2015-11-27 8:10 ` Lukas Pirl
2015-11-27 9:16 ` Anand Jain
2015-11-27 17:19 ` Christoph Anton Mitterer
2015-11-30 14:01 ` Anand Jain [this message]
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=565C56B6.7010106@oracle.com \
--to=anand.jain@oracle.com \
--cc=calestyo@scientia.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.