Files
apfstests/tests/btrfs/190
T
Filipe Manana 8c16b061f7 btrfs: make all btrfs tests that exercise balance use _run_btrfs_balance_start()
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>
2020-04-20 00:40:59 +08:00

94 lines
2.2 KiB
Bash
Executable File

#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2019 SUSE Linux Products GmbH. All Rights Reserved.
#
# FS QA Test 190
#
# A general test to validate that balance and qgroups work correctly when
# balance needs to be resumed on mount.
#
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
. ./common/dmlogwrites
# 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
# and we need extra device as log device
_require_log_writes
nr_files=512 # enough metadata to bump tree height
file_size=2048 # small enough to be inlined
_log_writes_init $SCRATCH_DEV
_log_writes_mkfs >> $seqres.full 2>&1
_log_writes_mount
$BTRFS_UTIL_PROG quota enable $SCRATCH_MNT >> $seqres.full
$BTRFS_UTIL_PROG quota rescan -w $SCRATCH_MNT >> $seqres.full
# Create enough metadata for later balance
for ((i = 0; i < $nr_files; i++)); do
_pwrite_byte 0xcd 0 $file_size $SCRATCH_MNT/file_$i > /dev/null
done
# Flush delalloc so that balance has work to do.
sync
# Balance metadata so we will have at least one transaction committed with
# valid reloc tree, and hopefully another commit with orphan reloc tree.
_run_btrfs_balance_start -f -m $SCRATCH_MNT >> $seqres.full
_log_writes_unmount
_log_writes_remove
cur=$(_log_writes_find_next_fua 0)
echo "cur=$cur" >> $seqres.full
while [ ! -z "$cur" ]; do
_log_writes_replay_log_range $cur $SCRATCH_DEV >> $seqres.full
# Test that no crashes happen or any other kind of failure.
_scratch_mount
_scratch_unmount
# Don't trigger fsck here, as relocation get paused,
# at that transistent state, qgroup number may differ
# and cause false alert.
prev=$cur
cur=$(_log_writes_find_next_fua $(($cur + 1)))
[ -z "$cur" ] && break
done
# Now the fs has finished its balance and qgroup should be consistent.
# Fstest will automatically check the fs and btrfs check will report
# any qgroup inconsistent if something went wrong.
echo "Silence is golden"
# success, all done
status=0
exit