From: Filipe Manana <fdmanana@xxxxxxxx> There's no need to have an explicit scratch filesystem sync and unmount at the of the test, as the fstests framework automatically unmounts the filesystem and the unmount naturally syncs any data and metadata. So remove them and update the comment to be more clear. Signed-off-by: Filipe Manana <fdmanana@xxxxxxxx> --- tests/btrfs/028 | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/tests/btrfs/028 b/tests/btrfs/028 index 8fbe8887..0c96b2fe 100755 --- a/tests/btrfs/028 +++ b/tests/btrfs/028 @@ -48,11 +48,8 @@ kill $fsstress_pid &> /dev/null wait $fsstress_pid &> /dev/null _btrfs_kill_stress_balance_pid $balance_pid -_run_btrfs_util_prog filesystem sync $SCRATCH_MNT - -_scratch_unmount - -# qgroup will be checked at _check_scratch_fs() by fstest. +# The qgroups accounting will be checked by 'btrfs check' (fsck) after the +# fstests framework unmounts the filesystem. echo "Silence is golden" status=0 -- 2.43.0
