From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 0/3] btrfs: fix false alerts when running with 8K block size and 4K page size
Date: Fri, 19 Sep 2025 08:13:24 +0930 [thread overview]
Message-ID: <20250918224327.12979-1-wqu@suse.com> (raw)
I am developing the bs > ps support for btrfs, and now it can pass most
btrfs and generic runs.
Some failures are due to the limitaions of the current bs > ps,
including:
- btrfs/023
No RAID56 support, and the test case doesn't respect
BTRFS_PROFILE_CONFIGS
- btrfs/131
No v1 cache support just like subpage bs support.
No big deal, as v1 cache is already marked deprecated.
When the full deprecation comes, the test case needs some update.
- btrfs/226
No Direct IO support.
- btrfs/267
No Direct IO support thus the read falls back to buffered one.
The fallback may change the pid thus some mirror is not properly read
from disk and no read repair.
- btrfs/281
No encoded send support
However there are some btrfs failures that are false alerts:
- btrfs/012
- btrfs/136
Those are btrfs-convert tests, however ext* doesn't support bs > ps
cases yet.
Fix them by skip the run if the initial ext* mount failed.
- btrfs/192
This one requires 4K nodesize, which implies 4K block size, and
conflicts with user specified non-4K block size.
- btrfs/30[456]
Those test cases have strict 4K block size requirement but still
follows the user specified block size during mkfs.
Fix btrfs/192 and btrfs/30[456] by explicitly specify 4K block size
during mkfs.
There is also a minor comment mismatch in btrfs/267:
- btrfs/267 is verifying direct read repair but comments says buffered
Instead it's btrfs/266 verifying the buffered behavior.
So it's purely a comment mismatch.
Fix it by explicitly mentioning buffered/direct IO for btrfs/26[67].
Qu Wenruo (3):
btrfs/012 btrfs/136: skip the test if ext* doesn't support the block
size
btrfs/192 btrfs/30[456]: explicitly specify block size to avoid false
alerts
btrfs/26[67]: update the stale comments
tests/btrfs/012 | 3 +++
tests/btrfs/136 | 3 +++
tests/btrfs/192 | 8 ++------
tests/btrfs/266 | 4 ++--
tests/btrfs/267 | 2 +-
tests/btrfs/304 | 5 ++---
tests/btrfs/305 | 5 ++---
tests/btrfs/306 | 5 ++---
8 files changed, 17 insertions(+), 18 deletions(-)
--
2.51.0
next reply other threads:[~2025-09-18 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 22:43 Qu Wenruo [this message]
2025-09-18 22:43 ` [PATCH 1/3] btrfs/012 btrfs/136: skip the test if ext* doesn't support the block size Qu Wenruo
2025-09-28 14:54 ` Zorro Lang
2025-09-28 20:42 ` Qu Wenruo
2025-10-01 20:50 ` Zorro Lang
2025-10-01 21:11 ` Qu Wenruo
2025-09-18 22:43 ` [PATCH 2/3] btrfs/192 btrfs/30[456]: explicitly specify block size to avoid false alerts Qu Wenruo
2025-09-28 14:12 ` Zorro Lang
2025-09-18 22:43 ` [PATCH 3/3] btrfs/26[67]: update the stale comments Qu Wenruo
2025-09-28 14:09 ` Zorro Lang
-- strict thread matches above, loose matches on Subject: below --
2025-09-18 22:33 [PATCH 0/3] btrfs: fix false alerts when running with 8K block size and 4K page size Qu Wenruo
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=20250918224327.12979-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=fstests@vger.kernel.org \
--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).