From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: Duncan <1i5t5.duncan@cox.net>
Subject: Re: [PATCH v2 3/3] btrfs-progs: device: add remove missing-all
Date: Mon, 16 Oct 2017 11:30:52 +0800 [thread overview]
Message-ID: <d311a713-a663-a11d-7cdb-bb9d359c4ba5@oracle.com> (raw)
In-Reply-To: <pan$48dd8$f51614da$34e59787$eb10b745@cox.net>
On 10/13/2017 01:27 PM, Duncan wrote:
> Misono, Tomohiro posted on Wed, 11 Oct 2017 11:18:50 +0900 as excerpted:
>
>> Add 'btrfs remove missing-all' to remove all the missing devices at once
>> for improving usability.
>>
>> Example:
>> sudo mkfs.btrfs -f -d raid1 /dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
>> sudo wipefs -a /dev/sdb1 /dev/sdb3
>> sudo mount -o degraded /dev/sdb2 /mnt <--
I agree with Duncan here. This step itself will fail even with RO
option. Do you have any patch that is not in the ML which will
make this step a success in the first place ?
Thanks, Anand
>> sudo btrfs filesystem show /mnt
>> sudo btrfs device remove missing-all /mnt
>> sudo btrfs filesystem show /mnt
>
>
> There's a reason remove missing-all hasn't yet been implemented.
>
> Note that the above would be very unlikely to work once a filesystem has
> been used in any significant way, because raid1 and raid10 are explicitly
> chunk pairs, *NOT* duplicated N times across N devices. So with two
> devices missing, chances are that both copies of some chunks will be
> missing as well, so the filesystem would no longer be mountable degraded-
> writable, only degraded-readonly, in which case device remove won't work
> at all because the filesystem is readonly.
>
> In fact, until the recent per-chunk check patches went in, it was
> impossible to mount-writable a raid1 missing two devices at all, because
> the safeguards simply assumed some chunks would be entirely missing.
>
> The only case in which more than a single device missing is likely to be
> mountable degraded-writable (so device remove will work at all) is raid6,
> tho with recent patches there's narrow cases in which it /might/ be
> doable with raid1 as well.
>
> Now you may still wish to implement remove missing-all for raid6 mode and
> for the unusual corner-case raid1/raid10 in which it might work, but the
> documentation should be pretty clear that save for raid6 it can't be
> expected to work in most cases.
>
> Given that, I think remove missing-all hasn't been implemented as it
> simply hasn't been considered to be worth the bother for the narrow use-
> cases in which it will actually work.
>
next prev parent reply other threads:[~2017-10-16 3:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 2:14 [PATCH v2 0/3] btrfs-progs: device: update btrfs device remove missing Misono, Tomohiro
2017-10-11 2:16 ` [PATCH v2 1/3] btrfs-progs: device: add description of alias to help message Misono, Tomohiro
2017-10-11 2:17 ` [PATCH v2 2/3] btrfs-progs: doc: add description of missing and example of device remove Misono, Tomohiro
2017-10-11 2:18 ` [PATCH v2 3/3] btrfs-progs: device: add remove missing-all Misono, Tomohiro
2017-10-13 5:27 ` Duncan
2017-10-16 3:30 ` Anand Jain [this message]
2017-10-16 4:35 ` Misono, Tomohiro
2017-10-16 6:46 ` Anand Jain
2017-10-16 14:16 ` Duncan
2017-10-16 4:32 ` Misono, Tomohiro
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=d311a713-a663-a11d-7cdb-bb9d359c4ba5@oracle.com \
--to=anand.jain@oracle.com \
--cc=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 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).