diff options
author | Naohiro Aota <naohiro.aota@wdc.com> | 2023-09-26 23:11:47 +0900 |
---|---|---|
committer | Zorro Lang <zlang@kernel.org> | 2023-10-05 22:37:12 +0800 |
commit | 7a093dfa66d61ad107235161a5a52444d361e387 (patch) | |
tree | 8687b7c1beed69e02c070cf7e3bc3e116b88a54e | |
parent | 0b70188b651b8d918989d35d162927051b5ff1bb (diff) | |
download | xfstests-dev-7a093dfa66d61ad107235161a5a52444d361e387.tar.gz |
btrfs/295: skip on zoned device as we cannot corrupt it directly
We use _pwrite_byte to corrupt the root node, but such overwrite won't work
on a sequential write required zone. So, skip the test on a zoned device.
Technically, we can run this test case by checking if the physical location
lands in a conventional zone. But, the logic should be no difference than
the regular mode and I don't think it's worth doing so.
Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Signed-off-by: Zorro Lang <zlang@kernel.org>
-rwxr-xr-x | tests/btrfs/295 | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/btrfs/295 b/tests/btrfs/295 index a9a8e5530a..00a5c5680b 100755 --- a/tests/btrfs/295 +++ b/tests/btrfs/295 @@ -12,6 +12,8 @@ _begin_fstest auto quick dangerous . ./common/filter _supported_fs btrfs _require_scratch +# Directly writing to the device, which may not work with a zoned device +_require_non_zoned_device "$SCRATCH_DEV" # Use single metadata profile so we only need to corrupt one copy of tree block _scratch_mkfs -m single > $seqres.full |