From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 3/3] btrfs-progs: device: add remove missing-all
Date: Mon, 16 Oct 2017 14:16:47 +0000 (UTC) [thread overview]
Message-ID: <pan$42eea$de4d7a4f$758b6722$69270df6@cox.net> (raw)
In-Reply-To: 649452a3-908d-670d-8bfd-b0e248b32b32@jp.fujitsu.com
Misono, Tomohiro posted on Mon, 16 Oct 2017 13:35:08 +0900 as excerpted:
> On 2017/10/16 12:30, Anand Jain wrote:
>>
>>
>> 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
>>
>>
> commit 21634a19f646 ("btrfs: Introduce a function to check if all chunks
> a OK for degraded rw mount") allow this from 4.14 (I checked on
> 4.14-rc4).
That's why I said recent patches allow it in corner-cases. However, I
think those corner-cases would I think be difficult to document concisely
in the manpage, and without that, I believe the option would be more
confusing than helpful, since people would expect it to actually work
when it won't, for them.
> But I will withdraw this patch as Duncan suggests.
If someone comes up with a satisfactory way to explain at a manpage level
the corner-cases in which removing more than one missing device at a time
can work...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-10-16 14:17 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
2017-10-16 4:35 ` Misono, Tomohiro
2017-10-16 6:46 ` Anand Jain
2017-10-16 14:16 ` Duncan [this message]
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='pan$42eea$de4d7a4f$758b6722$69270df6@cox.net' \
--to=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).