Files
apfstests/tests/btrfs/013
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

71 lines
1.7 KiB
Bash
Executable File

#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2013 Fusion IO. All Rights Reserved.
#
# FS QA Test No. btrfs/013
#
# Regression test for balance with prealloc extents. This checks to make sure
# we are balacing prealloc'ed extents properly by making sure we don't have any
# csum errors. Unfortunately this manifests itself with no csum which means
# userspace doesn't get an error when reading the file back so we have to grok
# dmesg to see if there was a csum error.
#
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
here=`pwd`
tmp=/tmp/$$
status=1 # failure is the default!
_cleanup()
{
rm -f $tmp.*
}
trap "_cleanup ; exit \$status" 0 1 2 3 15
# get standard environment, filters and checks
. ./common/rc
. ./common/filter
# real QA test starts here
_supported_fs btrfs
_supported_os Linux
_require_scratch
rm -f $seqres.full
_scratch_mkfs > /dev/null 2>&1
_scratch_mount
nr_csum_no_found=$(dmesg | grep -c "no csum found")
nr_csum_failed=$(dmesg | grep -c "csum failed")
_check_csum_error()
{
new_csum_no_found=$(dmesg | grep -c "no csum found")
new_csum_failed=$(dmesg | grep -c "csum failed")
if [ $nr_csum_no_found -eq $new_csum_no_found -a \
$nr_csum_failed -eq $new_csum_failed ]; then
return 0
fi
return 1
}
$XFS_IO_PROG -f -c "falloc 0 1M" -c "pwrite 16k 8k" -c "fsync" \
$SCRATCH_MNT/foo > $seqres.full 2>&1
_run_btrfs_balance_start $SCRATCH_MNT >> $seqres.full
_scratch_unmount
_scratch_mount
$XFS_IO_PROG -c "pread 0 1M" $SCRATCH_MNT/foo >> $seqres.full 2>&1 || \
_fail "pread failed"
# This sucks but unfortunately it is the only way to be sure something didn't go
# wrong.
_check_csum_error || _fail "csum detected, please check dmesg"
echo "Silence is golden"
status=0 ; exit