aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2023-10-03 12:57:45 +0100
committerZorro Lang <zlang@kernel.org>2023-10-05 22:32:01 +0800
commitd213e332a32b5d74034ca718e1add40a2443fde2 (patch)
treed9547f1674602498ccd89aa71ee58906315f657c
parentf55e46d62968a3881bbe469e46a254978f517561 (diff)
downloadxfstests-dev-d213e332a32b5d74034ca718e1add40a2443fde2.tar.gz
btrfs/192: use append operator to output log replay results to $seqres.full
After doing log replay, btrfs/192 is overwriting the $seqres.full file because it uses the plain ">" redirect operator, instead of an append ">>" redirect operator. As a consequence it is overriding the file and eliminating any previous output that may be useful to debug a test failure (such as the fsstress seed or mkfs results). So use >> instead of >. Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: Anand Jain <anand.jain@oracle.com> Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Zorro Lang <zlang@kernel.org>
-rwxr-xr-xtests/btrfs/1922
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/btrfs/192 b/tests/btrfs/192
index 80588a3c99..00ea1478ab 100755
--- a/tests/btrfs/192
+++ b/tests/btrfs/192
@@ -121,7 +121,7 @@ log_writes_fast_replay_check()
--replay $blkdev --check $check_point --fsck "$fsck_command" \
&> $tmp.full_fsck
ret=$?
- tail -n 150 $tmp.full_fsck > $seqres.full
+ tail -n 150 $tmp.full_fsck >> $seqres.full
[ $ret -ne 0 ] && _fail "fsck failed during replay"
}