Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: 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: Sat, 8 Jul 2023 06:17:11 +0800	[thread overview]
Message-ID: <33e2f4fa-3e1c-c249-8d8a-8d491da2f2e2@gmx.com> (raw)
In-Reply-To: <PR3PR04MB7340A2D0D9738902AC008CE0D62DA@PR3PR04MB7340.eurprd04.prod.outlook.com>



On 2023/7/8 04:48, Bernd Lentes wrote:
>
>> -----Original Message-----
>> From: Qu Wenruo <quwenruo.btrfs@gmx.com>
>> Sent: Thursday, July 6, 2023 8:20 AM
>> To: 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
>
>
>
>> Checksum have two functions:
>>
>> - Detect errors
>>    As long as it's not a false alert, then it makes sense.
>>    But please keep in mind that, a csum mismatch will prevent anyone
>>    from reading that corrupted data, whether this is the expected
>>    behavior really depends on your workload.
>>
>>    E.g. if some archive with built-in error detect and recovery (like RAR
>>    files), it's definitely not a good idea to return -EIO for the whole
>>    block, other than reading out the corrupted data and let the software
>>    to handle them.
>>
>> - Recover the good data from the extra mirrors
>>    This only works if you're using profiles with duplication (DUP,
>>    RAID1*, RAID10, RAID5, RAID6).
>>    Otherwise btrfs won't be able to recover anything.
>>
>> 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.
>>
>>> OK. I know which VM images produced checksum errors. I delete them and
>> restore them from the backup.
>>
>> You mentioned snapshots are utilized for those images, thus you have to
>> delete all the involved files, including ones in the snapshots.
>>
>>> So it finds errors in the data csum, correct ?
>>
>> Yes, either there are some files not deleted, or the file is snapshoted.
>
> I don't understand what you mean with that.

Is the file you deleted also in other snapshots?

And are you sure you deleted every file reported in dmesg by scrub?

Another possibility is, scrub reports can be ratelimited, thus some
files are not properly prompted.

Thanks,
Qu

>
> Thanks.
>
> Bernd
>
> Helmholtz Zentrum München – Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
> Ingolstädter Landstraße 1, D-85764 Neuherberg, https://www.helmholtz-munich.de
> Geschäftsführung: Prof. Dr. med. Dr. h.c. Matthias Tschöp, Daniela Sommer (komm.) | Aufsichtsratsvorsitzende: MinDir’in Prof. Dr. Veronika von Messling
> Registergericht: Amtsgericht München HRB 6466 | USt-IdNr. DE 129521671

  reply	other threads:[~2023-07-07 22:17 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
2023-07-07 20:48                   ` Bernd Lentes
2023-07-07 22:17                     ` Qu Wenruo [this message]
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=33e2f4fa-3e1c-c249-8d8a-8d491da2f2e2@gmx.com \
    --to=quwenruo.btrfs@gmx.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