From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: introduce rescue=all
Date: Wed, 9 Sep 2020 15:25:29 +0800 [thread overview]
Message-ID: <3dce83b1-bf02-e119-a549-20f6fd36643d@gmx.com> (raw)
In-Reply-To: <20200909072002.GD18399@twin.jikos.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1060 bytes --]
On 2020/9/9 下午3:20, David Sterba wrote:
> On Wed, Sep 09, 2020 at 07:10:49AM +0800, Qu Wenruo wrote:
>>
>>
>> On 2020/9/8 下午11:43, Josef Bacik wrote:
>>> One of the things that came up consistently in talking with Fedora about
>>> switching to btrfs as default is that btrfs is particularly vulnerable
>>> to metadata corruption. If any of the core global roots are corrupted,
>>> the fs is unmountable and fsck can't usually do anything for you without
>>> some special options.
>>>
>>> What we really want is a simple mount option we can tell all users to
>>> try if things are really wrong that are going to give them the highest
>>> chance of allowing them to mount their file system and copy off their
>>> data in the most direct way possible.
>>
>> Then "all" doesn't look correct for such usage.
>> I'd prefer "salvage" then.
>
> Let's focus on the functionality for now.
>
Then the code looks OK to me on the functionality part.
Maybe missing my sob line for the initial fill_dummy_bg() code...
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-09 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 15:43 [PATCH] btrfs: introduce rescue=all Josef Bacik
2020-09-08 23:10 ` Qu Wenruo
2020-09-09 7:20 ` David Sterba
2020-09-09 7:25 ` Qu Wenruo [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=3dce83b1-bf02-e119-a549-20f6fd36643d@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--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