linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Marc Oggier <marc.oggier@megavolts.ch>, linux-btrfs@vger.kernel.org
Subject: Re: Spare Volume Features
Date: Fri, 30 Aug 2019 16:07:28 +0800	[thread overview]
Message-ID: <32719c3e-6aa5-940f-6d53-59bab80d5ad5@oracle.com> (raw)
In-Reply-To: <0b7bfde0-0711-cee3-1ed8-a37b1a62bf5e@megavolts.ch>


  use-cases in production must need a spare device to maintain data
  redundancy in the event of volume disk failure, so this feature
  should be in btrfs.ko. And nntil we get there, workaround like
  monitor for write_io_errs and call for replace should help.

  HTH.

Thanks, Anand

      parent reply	other threads:[~2019-08-30  8:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29  0:51 Spare Volume Features Marc Oggier
2019-08-29  2:21 ` Sean Greenslade
2019-08-29 22:41   ` waxhead
2019-09-01  3:28   ` Sean Greenslade
2019-09-01  8:03     ` Andrei Borzenkov
2019-09-02  0:52       ` Sean Greenslade
2019-09-02  1:09         ` Chris Murphy
2019-09-03 11:35           ` Austin S. Hemmelgarn
2019-08-30  8:07 ` 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=32719c3e-6aa5-940f-6d53-59bab80d5ad5@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc.oggier@megavolts.ch \
    /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).