From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Nick Austin <nick@smartaustin.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Strange behavior when replacing device on BTRFS RAID 5 array.
Date: Mon, 27 Jun 2016 11:46:50 -0600 [thread overview]
Message-ID: <CAJCQCtTcDc2H3KYHe1oqT9QnZq2pt8Mn=SX6ZpMHT8bTPdE8_w@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtTY-vsZi_QmQ7gSpzkQfC9oPfPU1uqvf8madwDRPsCDJw@mail.gmail.com>
On Mon, Jun 27, 2016 at 11:29 AM, Chris Murphy <lists@colorremedies.com> wrote:
>
> Next is to decide to what degree you want to salvage this volume and
> keep using Btrfs raid56 despite the risks
Forgot to complete this thought. So if you get a backup, and decide
you want to fix it, I would see if you can cancel the replace using
"btrfs replace cancel <mp>" and confirm that it stops. And now is the
risky part, which is whether to try "btrfs add" and then "btrfs
remove" or remove the bad drive, reboot, and see if it'll mount with
-o degraded, and then use add and remove (in which case you'll use
'remove missing').
The first you risk Btrfs still using the flaky bad drive.
The second you risk whether a degraded mount will work, and whether
any other drive in the array has a problem while degraded (like an
unrecovery read error from a single sector).
--
Chris Murphy
next prev parent reply other threads:[~2016-06-27 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 3:57 Strange behavior when replacing device on BTRFS RAID 5 array Nick Austin
2016-06-27 4:02 ` Nick Austin
2016-06-27 17:29 ` Chris Murphy
2016-06-27 17:37 ` Austin S. Hemmelgarn
2016-06-27 17:46 ` Chris Murphy [this message]
2016-06-27 22:29 ` Steven Haigh
2016-06-27 21:12 ` 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='CAJCQCtTcDc2H3KYHe1oqT9QnZq2pt8Mn=SX6ZpMHT8bTPdE8_w@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nick@smartaustin.com \
/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).