@@ -461,3 +461,12 @@ _require_btrfs_sysfs_fsid()
test -f /sys/fs/btrfs/$fsid/devinfo/1/fsid ||\
_notrun "Need btrfs sysfs fsid support"
}
+
+_btrfs_no_v1_cache_opt()
+{
+ if $BTRFS_UTIL_PROG inspect-internal dump-tree $SCRATCH_DEV |\
+ grep -q "FREE_SPACE_TREE"; then
+ return
+ fi
+ echo -n "-onospace_cache"
+}
@@ -22,7 +22,7 @@ _scratch_mkfs >>$seqres.full 2>&1
# Mount our filesystem without space caches enabled so that we do not get any
# space used from the initial data block group that mkfs creates (space caches
# used space from data block groups).
-_scratch_mount "-o nospace_cache"
+_scratch_mount $(_btrfs_no_v1_cache_opt)
# Need an fs with at least 2Gb to make sure mkfs.btrfs does not create an fs
# using mixed block groups (used both for data and metadata). We really need
@@ -60,9 +60,8 @@ echo "step 1......mkfs.btrfs" >>$seqres.full
mkfs_opts="-d raid1 -b 1G"
_scratch_pool_mkfs $mkfs_opts >>$seqres.full 2>&1
-# -o nospace_cache makes sure data is written to the start position of the data
-# chunk
-_scratch_mount -o nospace_cache
+# make sure data is written to the start position of the data chunk
+_scratch_mount $(_btrfs_no_v1_cache_opt)
$XFS_IO_PROG -f -d -c "pwrite -S 0xaa -b 128K 0 128K" "$SCRATCH_MNT/foobar" |\
_filter_xfs_io_offset
@@ -59,9 +59,8 @@ _check_minimal_fs_size $(( 1024 * 1024 * 1024 ))
mkfs_opts="-d raid1 -b 1G"
_scratch_pool_mkfs $mkfs_opts >>$seqres.full 2>&1
-# -o nospace_cache makes sure data is written to the start position of the data
-# chunk
-_scratch_mount -o nospace_cache
+# make sure data is written to the start position of the data chunk
+_scratch_mount $(_btrfs_no_v1_cache_opt)
$XFS_IO_PROG -f -d -c "pwrite -S 0xaa -b 128K 0 128K" "$SCRATCH_MNT/foobar" |\
_filter_xfs_io_offset
@@ -37,9 +37,8 @@ _check_minimal_fs_size $(( 1024 * 1024 * 1024 ))
mkfs_opts="-d raid1 -b 1G"
_scratch_pool_mkfs $mkfs_opts >>$seqres.full 2>&1
-# -o nospace_cache makes sure data is written to the start position of the data
-# chunk
-_scratch_mount -o nospace_cache,nodatasum
+# make sure data is written to the start position of the data chunk
+_scratch_mount -o nodatasum $(_btrfs_no_v1_cache_opt)
$XFS_IO_PROG -f -d -c "pwrite -S 0xaa -b 128K 0 128K" "$SCRATCH_MNT/foobar" |\
_filter_xfs_io_offset
@@ -44,9 +44,8 @@ _check_minimal_fs_size $(( 1024 * 1024 * 1024 ))
mkfs_opts="-d raid1 -b 1G"
_scratch_pool_mkfs $mkfs_opts >>$seqres.full 2>&1
-# -o nospace_cache makes sure data is written to the start position of the data
-# chunk
-_scratch_mount -o nospace_cache,nodatasum
+# make sure data is written to the start position of the data chunk
+_scratch_mount -o nodatasum $(_btrfs_no_v1_cache_opt)
$XFS_IO_PROG -f -d -c "pwrite -S 0xaa -b 128K 0 128K" "$SCRATCH_MNT/foobar" |\
_filter_xfs_io_offset
@@ -31,8 +31,8 @@ _scratch_dev_pool_get 3
# create raid1 for data
_scratch_pool_mkfs "-d raid1 -b 1G" >> $seqres.full 2>&1
-# we need an empty data chunk, so nospace_cache is required.
-_scratch_mount -onospace_cache
+# we need an empty data chunk, so $(_btrfs_no_v1_cache_opt) is required.
+_scratch_mount $(_btrfs_no_v1_cache_opt)
# if data chunk is empty, 'btrfs device remove' can change raid1 to
# single.
@@ -64,9 +64,8 @@ _check_minimal_fs_size $(( 1024 * 1024 * 1024 ))
mkfs_opts="-d raid6 -b 1G"
_scratch_pool_mkfs $mkfs_opts >>$seqres.full 2>&1
-# -o nospace_cache makes sure data is written to the start position of the data
-# chunk
-_scratch_mount -o nospace_cache
+# make sure data is written to the start position of the data chunk
+_scratch_mount $(_btrfs_no_v1_cache_opt)
# [0,64K) is written to stripe 0 and [64K, 128K) is written to stripe 1
$XFS_IO_PROG -f -d -c "pwrite -S 0xaa 0 128K" -c "fsync" \
@@ -94,7 +93,7 @@ $XFS_IO_PROG -f -d -c "pwrite -S 0xbb $phy1 64K" $devpath1 > /dev/null
# step 3: read foobar to repair the bitrot
echo "step 3......repair the bitrot" >> $seqres.full
-_scratch_mount -o nospace_cache
+_scratch_mount $(_btrfs_no_v1_cache_opt)
# read the 2nd stripe, i.e. [64K, 128K), to trigger repair
od -x -j 64K $SCRATCH_MNT/foobar
@@ -56,9 +56,8 @@ _check_minimal_fs_size $(( 1024 * 1024 * 1024 ))
mkfs_opts="-d raid6 -b 1G"
_scratch_pool_mkfs $mkfs_opts >>$seqres.full 2>&1
-# -o nospace_cache makes sure data is written to the start position of the data
-# chunk
-_scratch_mount -o nospace_cache
+# make sure data is written to the start position of the data chunk
+_scratch_mount $(_btrfs_no_v1_cache_opt)
# [0,64K) is written to stripe 0 and [64K, 128K) is written to stripe 1
$XFS_IO_PROG -f -d -c "pwrite -S 0xaa 0 128K" -c "fsync" \
@@ -85,7 +84,7 @@ $XFS_IO_PROG -f -d -c "pwrite -S 0xbb $phy1 64K" $devpath1 > /dev/null
# step 3: scrub filesystem to repair the bitrot
echo "step 3......repair the bitrot" >> $seqres.full
-_scratch_mount -o nospace_cache
+_scratch_mount $(_btrfs_no_v1_cache_opt)
$BTRFS_UTIL_PROG scrub start -B $SCRATCH_MNT >> $seqres.full 2>&1
@@ -29,7 +29,7 @@ _scratch_mkfs_sized $fs_size >>$seqres.full 2>&1
# Mount without space cache so that we can precisely fill all data space and
# unallocated space later (space cache v1 uses data block groups).
-_scratch_mount "-o nospace_cache"
+_scratch_mount $(_btrfs_no_v1_cache_opt)
# Create our test file and allocate 1826.25Mb of space for it.
# This will exhaust the existing data block group and all unallocated space on
@@ -67,7 +67,7 @@ loop_dev=$(_create_loop_device "$loop_file")
loop_mnt=$tmp/loop_mnt
mkdir -p $loop_mnt
-# - nospace_cache
+# - $(_btrfs_no_v1_cache_opt)
# Since v1 cache using DATA space, it can break data extent bytenr
# continuousness.
# - nodatasum
@@ -75,7 +75,7 @@ mkdir -p $loop_mnt
# Disabling datasum could reduce the margin caused by metadata to minimal
# - discard
# What we're testing
-_mount -o nospace_cache,nodatasum,discard $loop_dev $loop_mnt
+_mount $(_btrfs_no_v1_cache_opt) -o nodatasum,discard $loop_dev $loop_mnt
# Craft the following extent layout:
# | BG1 | BG2 | BG3 |
@@ -30,7 +30,7 @@ _require_non_zoned_device $SCRATCH_DEV
_scratch_mkfs > /dev/null
# disable freespace inode to ensure file is the first thing in the data
# blobk group
-_scratch_mount -o nospace_cache
+_scratch_mount $(_btrfs_no_v1_cache_opt)
pagesize=$(get_page_size)
blocksize=$(_get_block_size $SCRATCH_MNT)
In the coming btrfs-progs v5.15 release, mkfs.btrfs will change to use v2 cache by default. However nospace_cache mount option will not work with v2 cache, as it would make v2 cache out of sync with on-disk used space. So mounting a btrfs with v2 cache using "nospace_cache" will make btrfs to reject the mount. There are quite some test cases relying on nospace_cache to prevent v1 cache to take up data space. For those test cases, we no longer need the "nospace_cache" mount option if the filesystem is already using v2 cache. Since v2 cache is using metadata space, it will no longer take up data space, thus no extra mount options for those test cases. By this, we can keep those existing tests to run without problem for both v1 and v2 cache. Signed-off-by: Qu Wenruo <wqu@suse.com> --- Changelog: v2: - Add _scratch_no_v1_cache_opt() function v3: - Add _require_btrfs_command for _scratch_no_v1_cache_opt() v4: - Remove _require_btrfs_command since it won't work in a sub-shell And since "btrfs inspect dump-tree" should be included in all non-EOF distros, there isn't much need for such requirement. - Rename the helper function to _btrfs_no_v1_cache_opt() --- common/btrfs | 9 +++++++++ tests/btrfs/102 | 2 +- tests/btrfs/140 | 5 ++--- tests/btrfs/141 | 5 ++--- tests/btrfs/142 | 5 ++--- tests/btrfs/143 | 5 ++--- tests/btrfs/151 | 4 ++-- tests/btrfs/157 | 7 +++---- tests/btrfs/158 | 7 +++---- tests/btrfs/170 | 2 +- tests/btrfs/199 | 4 ++-- tests/btrfs/215 | 2 +- 12 files changed, 30 insertions(+), 27 deletions(-)