From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Monitoring Btrfs
Date: Tue, 18 Oct 2016 08:41:01 -0400 [thread overview]
Message-ID: <e651a6d5-9d99-61f5-202b-95e37fae2ec8@gmail.com> (raw)
In-Reply-To: <CAJCQCtR97w1PDsMRSg_RkfjCL1J+ZTA4xAhMVZz1T-1JWwGiwA@mail.gmail.com>
On 2016-10-17 16:40, Chris Murphy wrote:
> May be better to use /sys/fs/btrfs/<uuid>/devices to find the device
> to monitor, and then monitor them with blktrace - maybe there's some
> courser granularity available there, I'm not sure. The thing is, as
> far as Btrfs alone is concerned, a drive can be "bad" and you're
> effectively degraded, while the drive is not missing. Unless it's
> physical removed or somehow dead, it'll still be seen but can produce
> all kinds of mayhem.
This is exactly why you should be monitoring the disks themselves, not
just BTRFS. I would not advise using blktrace for monitoring in
production though, it technically risks an information leak, and it's
not exactly low impact.
next prev parent reply other threads:[~2016-10-18 12:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 16:44 Monitoring Btrfs Stefan Malte Schumacher
2016-10-17 17:23 ` Austin S. Hemmelgarn
2016-10-18 3:23 ` Anand Jain
2016-10-18 12:39 ` Austin S. Hemmelgarn
2016-10-18 21:36 ` Anand Jain
2016-10-19 11:15 ` Austin S. Hemmelgarn
2016-10-19 13:06 ` Anand Jain
2016-10-19 13:33 ` Austin S. Hemmelgarn
2016-10-19 21:38 ` Anand Jain
2016-10-17 17:41 ` Zygo Blaxell
2016-10-17 17:55 ` Kyle Manna
2016-10-17 20:40 ` Chris Murphy
2016-10-18 12:41 ` Austin S. Hemmelgarn [this message]
2016-10-19 22:46 ` Stefan Malte Schumacher
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=e651a6d5-9d99-61f5-202b-95e37fae2ec8@gmail.com \
--to=ahferroin7@gmail.com \
--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 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).