| Message ID | 20221128125105.52458-1-johannes.thumshirn@wdc.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | fstests: skip btrfs/254 in case MIN_FSSIZE is more than 1G | expand |
On Mon, Nov 28, 2022 at 04:51:05AM -0800, Johannes Thumshirn wrote: > The test-case btrfs/254 creates a 1G device-mapper setup, but this might > be too small for the filesystem to actually operate (i.e. in case of a > zoned block device which needs at least 5 zones). > > Skip the test if MIN_FSSIZE is set to a value above 1G. > > Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Reviewed-by: Josef Bacik <josef@toxicpanda.com> Thanks, Josef
diff --git a/tests/btrfs/254 b/tests/btrfs/254 index 5d6e33f40bb5..ae55ae8ca3a2 100755 --- a/tests/btrfs/254 +++ b/tests/btrfs/254 @@ -40,6 +40,7 @@ _require_dm_target linear _require_btrfs_forget_or_module_loadable _require_scratch_nocheck _require_command "$WIPEFS_PROG" wipefs +_check_minimal_fs_size $((1024 * 1024 * 1024)) _scratch_dev_pool_get 3
The test-case btrfs/254 creates a 1G device-mapper setup, but this might be too small for the filesystem to actually operate (i.e. in case of a zoned block device which needs at least 5 zones). Skip the test if MIN_FSSIZE is set to a value above 1G. Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> --- tests/btrfs/254 | 1 + 1 file changed, 1 insertion(+)