From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Roman Mamedov <rm@romanrm.net>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC PATCH] btrfs: rescue: Introduce new rescue mount option, rescue=skipdatacsum, to skip data csum verification
Date: Tue, 29 Oct 2019 15:09:34 +0800 [thread overview]
Message-ID: <7136fdbf-364e-8b00-c078-fb77b1b9d751@gmx.com> (raw)
In-Reply-To: <20191029115317.03b43d94@natsu>
[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]
On 2019/10/29 下午2:53, Roman Mamedov wrote:
> On Tue, 29 Oct 2019 14:21:49 +0800
> Qu Wenruo <wqu@suse.com> wrote:
>
>> Here we introduce a new rescue= mount option to completely skip data
>> csum check.
>> Since data csum check is completely skipped, for profiles with extra
>> mirrors/copies, it will return the first copy only, which is not
>> optimized, but should be good enough for rescue usage.
>>
>> This option only affects data csum verification, doesn't affect data
>> csum calcuation, so new data write will still be protected by csum (if
>> it doesn't get affected by csum tree corruption).
>
> Maybe just make the "nodatasum" mount option skip verification of existing
> checksums as well? Actually before seeing this patch I believed "nodatasum"
> already does that.
Nodatasum only applies to new writes, doesn't affect existing csum
verification.
Normally nodatasum is just considered as a performance optimization, not
something we would like to use for rescue usage.
>
> Also for consistency note that datasum/nodatasum call it just "sum" in the
> mount option name, not "csum".
That makes sense.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-10-29 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 6:21 [RFC PATCH] btrfs: rescue: Introduce new rescue mount option, rescue=skipdatacsum, to skip data csum verification Qu Wenruo
2019-10-29 6:53 ` Roman Mamedov
2019-10-29 7:09 ` 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=7136fdbf-364e-8b00-c078-fb77b1b9d751@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
--cc=wqu@suse.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