From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>,
Qu Wenruo <wqu@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: question to btrfs scrub
Date: Thu, 6 Jul 2023 15:07:04 +0800 [thread overview]
Message-ID: <5e5941b0-bd9e-e64a-251b-0e90688378d6@gmx.com> (raw)
In-Reply-To: <CAA91j0VjUiXZJi=S2h7uox8sL3B84yNSw+9SLiL0AxntO3TDDQ@mail.gmail.com>
On 2023/7/6 15:04, Andrei Borzenkov wrote:
> On Thu, Jul 6, 2023 at 9:22 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>> In your case, since you're already using LVM, thus I believe the fs is
>> using default profiles (DUP for meta, SINGLE for data), thus there would
>> be no extra copy to recover from.
>>
>> So there is really error detection functionality lost if go nodatasum.
>>
>
> You probably mean, "error *correction*".
Oh, my bad, it's indeed error *correction*.
Thanks,
Qu
> Error detection will
> certainly be lost. And error detection is certainly useful to detect
> data corruption (that is not usually possible using traditional
> filesystems). Yes, it will not be possible to correct these errors on
> btrfs level without redundancy.
next prev parent reply other threads:[~2023-07-06 7:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 8:26 question to btrfs scrub Bernd Lentes
2023-06-29 9:08 ` Qu Wenruo
2023-06-30 9:59 ` Bernd Lentes
2023-06-30 10:16 ` Qu Wenruo
2023-07-04 16:03 ` Bernd Lentes
2023-07-04 17:00 ` Bernd Lentes
2023-07-04 22:19 ` Qu Wenruo
2023-07-05 8:39 ` Bernd Lentes
2023-07-05 8:45 ` Qu Wenruo
2023-07-05 15:01 ` Bernd Lentes
2023-07-05 17:53 ` Remi Gauvin
2023-07-06 6:23 ` Qu Wenruo
2023-07-06 13:18 ` Remi Gauvin
2023-07-07 21:02 ` Bernd Lentes
2023-07-07 20:54 ` Bernd Lentes
2023-07-08 5:08 ` Qu Wenruo
2023-07-18 15:34 ` Bernd Lentes
2023-07-07 20:40 ` Bernd Lentes
2023-07-06 6:19 ` Qu Wenruo
2023-07-06 7:04 ` Andrei Borzenkov
2023-07-06 7:07 ` Qu Wenruo [this message]
2023-07-07 20:48 ` Bernd Lentes
2023-07-07 22:17 ` Qu Wenruo
2023-06-29 9:12 ` Forza
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=5e5941b0-bd9e-e64a-251b-0e90688378d6@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=arvidjaar@gmail.com \
--cc=bernd.lentes@helmholtz-muenchen.de \
--cc=linux-btrfs@vger.kernel.org \
--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