在 2025/8/19 21:30, Nirjhar Roy (IBM) 写道:
When tested with block size/node size 64K on btrfs, then the test fails
with the folllowing error:
QA output created by 563
read/write
read is in range
-write is in range
+write has value of 8855552
+write is NOT in range 7969177.6 .. 8808038.4
write -> read/write
...
The slight increase in the amount of bytes that are written is because
of the increase in the the nodesize(metadata) and hence it exceeds
the tolerance limit slightly. Fix this by increasing the iosize.
Increasing the iosize increases the tolerance range and covers the
tolerance for btrfs higher node sizes.
Reported-by: Disha Goel <disgoel@xxxxxxxxxxxxx>
Signed-off-by: Nirjhar Roy (IBM) <nirjhar.roy.lists@xxxxxxxxx>
Looks good to me.
Just want to add some more analyze for the failure case.
For the test it writes 8M data with 5% tolerance (around 408K) with the
total writes.
With 64K block size (and it implies 64K metadata size) for btrfs, it
mean we can have at most 7 tree blocks of writes plus two super blocks
updated.
Considering the default metadata profile is DUP, doubling the metadata
writes, the real limit is only 3 tree blocks.
And when doing fsync, btrfs will create at least 2 new tree blocks, one
for the log tree root, and one for the log tree of the subvolume.
This is still inside the tolerance, thus the test case can still pass
for a lot of cases.
But if a full transaction commit is triggered, btrfs will need to create
at least 3 new tree blocks for root, extent and subvolume tree.
Depending on the mkfs config, it will increase to 7 tree blocks (free
space tree, block group tree, csum tree and uuid tree created at mount).
All are exceeding the tolerance limit.
Doubling the io size will make the tolerance to be 8 tree blocks,
covering the worst case of 64K metadata sized btrfs, at least for now.
Reviewed-by: Qu Wenruo <wqu@xxxxxxxx>
Thanks,
Qu
---
tests/generic/563 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/generic/563 b/tests/generic/563
index 89a71aa4..6cb9ddb0 100755
--- a/tests/generic/563
+++ b/tests/generic/563
@@ -43,7 +43,7 @@ _require_block_device $SCRATCH_DEV
_require_non_zoned_device ${SCRATCH_DEV}
cgdir=$CGROUP2_PATH
-iosize=$((1024 * 1024 * 8))
+iosize=$((1024 * 1024 * 16))
# Check cgroup read/write charges against expected values. Allow for some
# tolerance as different filesystems seem to account slightly differently.
