From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christoph Hellwig <hch@lst.de>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Random RAID1C3 subpage read repair failure (btrfs/266)
Date: Tue, 6 Jun 2023 08:56:43 +0800 [thread overview]
Message-ID: <2bb2dba6-b4d6-0298-a960-020d846878a2@gmx.com> (raw)
Hi guys,
With recently resumed subpage tests, I'm hitting random failure in
btrfs/266 with subpage tests only. (64K page size with 4K sector size)
The failure rate is around 1/3 ~ 1/5, a "./check -I 10 btrfs/266" run is
always ensured to trigger a failure.
The most common (if not the only) failure is that mirror 3 didn't get
repaired, while mirror 1/2 are properly repaired.
The dmesg doesn't provide enough info since it's rated limited.
What makes it more weird is, the test case itself is already considering
subpage/larger page size, thus except the final verification, everything
is done in 64K block size.
But still it failed to be reproduced on x86_64.
I'm still actively investigating the bug, but if anyone has some clue
it's would be very appreciated.
Thanks,
Qu
reply other threads:[~2023-06-06 0:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2bb2dba6-b4d6-0298-a960-020d846878a2@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=hch@lst.de \
--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).