From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Dmitry Katsubo <dma_k@mail.ru>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Spare volumes and hot auto-replacement feature
Date: Thu, 5 May 2016 07:23:11 -0400 [thread overview]
Message-ID: <008f1f81-df20-796f-a609-78075ddd9837@gmail.com> (raw)
In-Reply-To: <572A8337.1030505@mail.ru>
On 2016-05-04 19:18, Dmitry Katsubo wrote:
> Dear btrfs community,
>
> I am interested in spare volumes and hot auto-replacement feature [1]. I have a couple of questions:
>
> * Which kernel version this feature will be included?
Probably 4.7. I would not suggest using it in production for at least a
few cycles though (probably 4.9).
> * The description says that replacement happens automatically when there is any write failed or flush failed. Is it possible to control the ratio / number of such failures? (e.g. in case it was one-time accidental failure)
As far as I know, no, it just happens.
> * What happens if spare device is smaller then the (failing) device to be replaced?
I'm pretty sure that it doesn't get replaced.
> * What happens if during the replacement the spare device fails (write error)?
I'm not certain about this one.
> * Is it possible for root to be notified in case if drive replacement (successful or unsuccessful) took place? Actually this question is actual for me for overall write/flush failures on btrfs volume (btrfs monitor).
There isn't any built-in monitoring in BTRFS that I know of, there are a
couple of options though for monitoring. The simplest and probably most
reliable is to write a script to poll for changes in the error counts.
You can also check the filesystem mount options (without the hot-spare
functionality, if there's an error, the filesystem will (usually) get
remounted read-only, and this also works for most other filesystems too).
next prev parent reply other threads:[~2016-05-05 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 23:18 Spare volumes and hot auto-replacement feature Dmitry Katsubo
2016-05-05 11:23 ` Austin S. Hemmelgarn [this message]
2016-05-06 9:08 ` David Sterba
2016-05-06 11:19 ` Austin S. Hemmelgarn
2016-05-05 15:35 ` Anand Jain
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=008f1f81-df20-796f-a609-78075ddd9837@gmail.com \
--to=ahferroin7@gmail.com \
--cc=dma_k@mail.ru \
--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).