From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Raid 5/6 Stability
Date: Thu, 24 Dec 2015 03:56:14 +0000 (UTC) [thread overview]
Message-ID: <pan$2d5fe$ffbfbbce$27af325f$ba6c76e8@cox.net> (raw)
In-Reply-To: CAJCQCtR=ydFe0w4MUAS6CGZeOe3wMMmijOW=qptF20uDZaSMyA@mail.gmail.com
Chris Murphy posted on Wed, 23 Dec 2015 19:38:23 -0700 as excerpted:
> There's a worthwhile distinction between stability of raid56 vs all
> other profiles, and btrfs multiple device failure behavior. Right now
> there's no monitoring or notification of failures to user space. In
> fact Btrfs itself doesn't really understand device failures, a device
> can spit out many read or write errors and Btrfs keeps trying to read
> and write. So there's no equivalent to faultiness like with md/mdadm.
> Therefore you'll have to figure out a way to monitor kernel messages,
> maybe via a script that parses for btrfs messages and emails any such
> messages ever 10m or whatever.
Absolutely. Raid56 mode may be stabilizing, but there's still no user-
side multi-device filesystem health monitoring application, either for
raid56 or in general, for the raid1/10 modes which are in fact reasonably
stable and mature on btrfs and have been considered at the level of btrfs
itself for quite awhile (several years), now.
Thanks for that addendum, Chris. It could be quite helpful to someone
just setting up a new installation, particularly on a server where the
user and/or admin is unlikely to be directly observing things and thus
know when things go wrong due to the observed change in behavior,
regardless of formal monitoring or the lack thereof, as would likely be
the case on a desktop/workstation.
--
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:[~2015-12-24 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 22:52 Raid 5/6 Stability jwalmer
2015-12-24 0:38 ` Duncan
2015-12-24 2:38 ` Chris Murphy
2015-12-24 3:56 ` Duncan [this message]
2015-12-24 10:29 ` Gerald Hopf
2015-12-24 13:56 ` jwalmer
2015-12-25 0:48 ` 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$2d5fe$ffbfbbce$27af325f$ba6c76e8@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.