From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
dsterba@suse.cz, David Sterba <dsterba@suse.com>,
anand.jain@oracle.com, rbrown@suse.de,
Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] btrfs-progs: warn users about the possible dangers of check --repair
Date: Tue, 22 Oct 2019 10:50:21 +0300 [thread overview]
Message-ID: <399c076f-4f31-936f-b02e-ecd2dbdb4a0f@suse.com> (raw)
In-Reply-To: <baccc7ef-2058-d779-7ce2-b2c120abefe4@gmx.com>
On 22.10.19 г. 10:37 ч., Qu Wenruo wrote:
>
>
> On 2019/10/22 下午3:33, Johannes Thumshirn wrote:
>> On 21/10/2019 17:22, David Sterba wrote:
>>> --force was added for a different reason, to allow check on a mounted
>>> filesystem. I don't think that combining --repair and --force just to
>>> allow repair is a good idea. There's a 'dangerous repair' mode for eg.
>>> xfs that allows to do live surgery on a mounted filesytem (followed by
>>> immediate reboot). We want to be able to do that eventually.
>>>
>>> I understand where the motivation comes from, let me have a second
>>> thought on that.
>>
>> So how about adding a '--yes' or '--accept', '--dangerous',
>> '--allow-dangeruos' parameter instead of force to skip the warning?
>>
>> My vote would go for '--allow-dangerous'.
>
> +1 for '--yes', at least e2fsck has a similar '-y' option.
I'\m fine with --yes/-y. It's not just e2fsck but I've seen similar
options in other tools as well.
>
> Thanks,
> Qu
>
>>
>> Byte,
>> Johannes
>>
next prev parent reply other threads:[~2019-10-22 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 11:16 [PATCH v2 1/2] btrfs-progs: warn users about the possible dangers of check --repair Johannes Thumshirn
2019-10-18 11:16 ` [PATCH v2 2/2] btrfs-progs: docs: fix warning test Johannes Thumshirn
2019-10-21 15:22 ` [PATCH v2 1/2] btrfs-progs: warn users about the possible dangers of check --repair David Sterba
2019-10-22 7:33 ` Johannes Thumshirn
2019-10-22 7:37 ` Qu Wenruo
2019-10-22 7:45 ` Johannes Thumshirn
2019-10-22 7:50 ` Nikolay Borisov [this message]
2019-10-22 12:19 ` David Sterba
2019-11-15 12:53 ` David Sterba
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=399c076f-4f31-936f-b02e-ecd2dbdb4a0f@suse.com \
--to=nborisov@suse.com \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=rbrown@suse.de \
/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