From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Regression that causes data csum mismatch
Date: Tue, 13 Jun 2023 14:26:39 +0800 [thread overview]
Message-ID: <da414ecc-f329-48ec-94d2-67c94755effb@gmx.com> (raw)
Hi,
Recently I am testing scrub preparing for the incoming logical scrub.
But I noticed some rare and random test cases failure from scrub and
replace groups.
E.g. btrfs/072 has a chance of failure around 1/30.
Initially I thought it's my scrub patches screwing things up, but with
more digging, it turns out that it's real data corruption.
After scrubbing found errors, btrfs check --check-data-csum also reports
csum mismatch.
Furthermore this is profile independent, I have see all profiles hitting
such data corruption.
Currently trying to bisect, but 6.4-rc4 already shows the bug.
And I can reproduce the problem on both x86_64 and aarch64 (both 4K page
size)
Thanks,
Qu
next reply other threads:[~2023-06-13 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 6:26 Qu Wenruo [this message]
2023-06-13 6:27 ` Regression that causes data csum mismatch Qu Wenruo
2023-06-13 13:21 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-13 16:02 ` David Sterba
2023-06-13 22:17 ` Qu Wenruo
2023-06-15 15:32 ` David Sterba
2023-06-15 18:00 ` Linux regression tracking (Thorsten Leemhuis)
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=da414ecc-f329-48ec-94d2-67c94755effb@gmx.com \
--to=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).