@@ -496,3 +496,14 @@ _require_btrfs_support_sectorsize()
grep -wq $sectorsize /sys/fs/btrfs/features/supported_sectorsizes || \
_notrun "sectorsize $sectorsize is not supported"
}
+
+# Require trigger for cleaner kthread
+_require_btrfs_debug_cleaner_trigger()
+{
+ local fsid
+
+ fsid=$($BTRFS_UTIL_PROG filesystem show $TEST_DIR | grep uuid: |\
+ $AWK_PROG '{print $NF}')
+ test -f /sys/fs/btrfs/$fsid/debug/cleaner_trigger ||\
+ _notrun "no cleaner kthread trigger"
+}
new file mode 100755
@@ -0,0 +1,112 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (C) 2022 SUSE Linux Products GmbH. All Rights Reserved.
+#
+# FS QA Test 256
+#
+# Make sure btrfs auto defrag can properly defrag clusters which has hole
+# in the middle
+#
+. ./common/preamble
+_begin_fstest auto defrag quick
+
+. ./common/btrfs
+. ./common/filter
+
+# real QA test starts here
+
+# Modify as appropriate.
+_supported_fs generic
+_require_scratch
+
+get_extent_disk_sector()
+{
+ local file=$1
+ local offset=$2
+
+ $XFS_IO_PROG -c "fiemap $offset" "$file" | _filter_xfs_io_fiemap |\
+ head -n1 | $AWK_PROG '{print $3}'
+}
+
+# Needs 4K sectorsize, as larger sectorsize can change the file layout.
+_require_btrfs_support_sectorsize 4096
+
+# We need a way to trigger autodefrag
+_require_btrfs_debug_cleaner_trigger
+
+_scratch_mkfs >> $seqres.full
+
+# Need datacow to show which range is defragged, and we're testing
+# autodefrag
+_scratch_mount -o datacow,autodefrag
+
+fsid=$($BTRFS_UTIL_PROG filesystem show $SCRATCH_MNT |grep uuid: |\
+ $AWK_PROG '{print $NF}')
+
+# Create a layout where we have fragmented extents at [0, 64k) (sync write in
+# reserve order), then a hole at [64k, 128k)
+$XFS_IO_PROG -f -c "pwrite 48k 16k" -c sync \
+ -c "pwrite 32k 16k" -c sync \
+ -c "pwrite 16k 16k" -c sync \
+ -c "pwrite 0 16k" $SCRATCH_MNT/foobar >> $seqres.full
+truncate -s 128k $SCRATCH_MNT/foobar
+sync
+
+old_csum=$(_md5_checksum $SCRATCH_MNT/foobar)
+echo "=== File extent layout before autodefrag ===" >> $seqres.full
+$XFS_IO_PROG -c "fiemap -v" "$SCRATCH_MNT/foobar" >> $seqres.full
+echo "old md5=$old_csum" >> $seqres.full
+
+old_regular=$(get_extent_disk_sector "$SCRATCH_MNT/foobar" 0)
+old_hole=$(get_extent_disk_sector "$SCRATCH_MNT/foobar" 64k)
+
+# For hole only xfs_io fiemap, there will be no output at all.
+# Re-fill it to "hole" for later comparison
+if [ ! -z $old_hole ]; then
+ echo "hole not at 128k"
+else
+ old_hole="hole"
+fi
+
+# Now trigger autodefrag
+echo 0 > /sys/fs/btrfs/$fsid/debug/cleaner_trigger
+
+# No good way to wait for autodefrag to finish yet
+sleep 3
+sync
+
+new_csum=$(_md5_checksum $SCRATCH_MNT/foobar)
+new_regular=$(get_extent_disk_sector "$SCRATCH_MNT/foobar" 0)
+new_hole=$(get_extent_disk_sector "$SCRATCH_MNT/foobar" 64k)
+
+echo "=== File extent layout after autodefrag ===" >> $seqres.full
+$XFS_IO_PROG -c "fiemap -v" "$SCRATCH_MNT/foobar" >> $seqres.full
+echo "new md5=$new_csum" >> $seqres.full
+
+if [ ! -z $new_hole ]; then
+ echo "hole not at 128k"
+else
+ new_hole="hole"
+fi
+
+# In v5.11~v5.15 kernels, regular extents won't get defragged, and would trigger
+# the following output
+if [ $new_regular == $old_regular ]; then
+ echo "regular extents didn't get defragged"
+fi
+
+# In v5.10 and earlier kernel, autodefrag may choose to defrag holes,
+# which should be avoided.
+if [ "$new_hole" != "$old_hole" ]; then
+ echo "hole extents got defragged"
+fi
+
+# Defrag should not change file content
+if [ "$new_csum" != "$old_csum" ]; then
+ echo "file content changed"
+fi
+
+echo "Silence is golden"
+# success, all done
+status=0
+exit
new file mode 100644
@@ -0,0 +1,2 @@
+QA output created by 256
+Silence is golden
In v5.11~v5.15 kernels, there is a regression in autodefrag that if a cluster (up to 256K in size) has even a single hole, the whole cluster will be rejected. This will greatly reduce the efficiency of autodefrag. The behavior is fixed in v5.16 by a full rework, although the rework itself has other problems, it at least solves this particular regression. Here we add a test case to reproduce the case, where we have a 128K cluster, the first half is fragmented extents which can be defragged. The second half is hole. Make sure autodefrag can defrag the 64K part. This test needs extra debug feature, which is titled: [RFC] btrfs: sysfs: introduce <uuid>/debug/cleaner_trigger Signed-off-by: Qu Wenruo <wqu@suse.com> --- common/btrfs | 11 +++++ tests/btrfs/256 | 112 ++++++++++++++++++++++++++++++++++++++++++++ tests/btrfs/256.out | 2 + 3 files changed, 125 insertions(+) create mode 100755 tests/btrfs/256 create mode 100644 tests/btrfs/256.out