mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Filipe Manana
8c16b061f7
In btrfs-progs v4.10 we had a behaviour change where starting a balance
operation without any filters results in a delay of 10 seconds and a
warning is printed to stdout that warns that a full balance is about to
be made and that it can be a slow operation. The new flag '--full-balance'
was added in that release to avoid the 10 seconds delay and the warning
message.
Our existing helper _run_btrfs_balance_start() uses that new balance flag
if we are running a btrfs-progs version that has it, to avoid that 10
seconds wait.
Make all existing btrfs tests that trigger balance operations use the
_run_btrfs_balance_start() helper, so that we avoid wasting time and
speed up some of the tests. In particular test btrfs/014 is now about 10x
faster and tests btrfs/060 to btrfs/064 3 to 5 times faster (depending
on the fsstress random load).
Besides speeding up many tests that do balance operations it also fixes
functional problems:
1) Since btrfs-progs v4.10 the test case btrfs/014 got broken, because
its purpose is to run balance and snapshot creation in parallel,
and that wasn't happening anymore because all snapshots were being
created during the 10 seconds delay of the first balance operation,
so balance and snapshot creation was being serialized instead of
running in parallel.
Fixing this test to avoid the 10 seconds delay immediately
exposes a regression that went into kernel 5.7-rc1 which is fixed
by the following commit
aec7db3b13a0 ("btrfs: fix setting last_trans for reloc roots")
2) Test cases btrfs/060 to btrfs/064 now spend much more time running
fsstress, balance and other operations in parallel, there's no
longer intervals of 10 seconds where balance is not running
concurrently with those other operations, making the tests a lot
more useful again.
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
70 lines
1.6 KiB
Bash
Executable File
70 lines
1.6 KiB
Bash
Executable File
#! /bin/bash
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
# Copyright (c) 2016 Fujitsu. All Rights Reserved.
|
|
#
|
|
# FS QA Test 123
|
|
#
|
|
# Test if btrfs leaks qgroup numbers for data extents
|
|
#
|
|
# Due to balance code is doing trick tree block swap, which doing
|
|
# non-standard extent reference update, qgroup can't handle it correctly,
|
|
# and leads to corrupted qgroup numbers.
|
|
#
|
|
seq=`basename $0`
|
|
seqres=$RESULT_DIR/$seq
|
|
echo "QA output created by $seq"
|
|
|
|
here=`pwd`
|
|
tmp=/tmp/$$
|
|
status=1 # failure is the default!
|
|
trap "_cleanup; exit \$status" 0 1 2 3 15
|
|
|
|
_cleanup()
|
|
{
|
|
cd /
|
|
rm -f $tmp.*
|
|
}
|
|
|
|
# get standard environment, filters and checks
|
|
. ./common/rc
|
|
. ./common/filter
|
|
|
|
# remove previous $seqres.full before test
|
|
rm -f $seqres.full
|
|
|
|
# real QA test starts here
|
|
|
|
# Modify as appropriate.
|
|
_supported_fs btrfs
|
|
_supported_os Linux
|
|
_require_scratch
|
|
_require_btrfs_qgroup_report
|
|
|
|
_scratch_mkfs >/dev/null
|
|
# Need to use inline extents to fill metadata rapidly
|
|
_scratch_mount "-o max_inline=2048"
|
|
|
|
# create 64K inlined metadata, which will ensure there is a 2-level
|
|
# metadata. Even for maximum nodesize(64K)
|
|
for i in $(seq 32); do
|
|
_pwrite_byte 0xcdcdcdcd 0 2k $SCRATCH_MNT/small_$i | _filter_xfs_io
|
|
done
|
|
|
|
# then a large data write to make the quota corruption obvious enough
|
|
_pwrite_byte 0xcdcdcdcd 0 32m $SCRATCH_MNT/large | _filter_xfs_io
|
|
sync
|
|
|
|
# enable quota and rescan to get correct number
|
|
_run_btrfs_util_prog quota enable $SCRATCH_MNT
|
|
_run_btrfs_util_prog quota rescan -w $SCRATCH_MNT
|
|
|
|
# now balance data block groups to corrupt qgroup
|
|
_run_btrfs_balance_start -d $SCRATCH_MNT >> $seqres.full
|
|
|
|
_scratch_unmount
|
|
# qgroup will be check at _check_scratch_fs() by fstest
|
|
|
|
# success, all done
|
|
status=0
|
|
exit
|