All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Dmitry Katsubo <dma_k@mail.ru>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Spare volumes and hot auto-replacement feature
Date: Thu, 5 May 2016 23:35:43 +0800	[thread overview]
Message-ID: <572B684F.5010306@oracle.com> (raw)
In-Reply-To: <572A8337.1030505@mail.ru>



Most of it (like policy tuning/configuring/notification) is through
sysfs interface, However to implement this, we need the existing sysfs
volume patches to be integrated.
We need to think about the implementation of per-FSID spare which I
hope will solve the problem incompatible spare disk.
As of now if auto replace fails, spare device is out of the kernel
device list. If user wants to give a 2nd try then, they should run
btrfs dev scan again. And the degraded vol will continue to look
for the spare device.

Thanks for the feedback.

Anand


On 05/05/2016 07:18 AM, 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?
> * 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)
> * What happens if spare device is smaller then the (failing) device to be replaced?
> * What happens if during the replacement the spare device fails (write error)?
> * 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).
>
> Many thanks!
>
> [1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg48209.html
>

      parent reply	other threads:[~2016-05-05 15:35 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
2016-05-06  9:08   ` David Sterba
2016-05-06 11:19     ` Austin S. Hemmelgarn
2016-05-05 15:35 ` 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=572B684F.5010306@oracle.com \
    --to=anand.jain@oracle.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 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.