From: Anand Jain <anand.jain@oracle.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 2/2] btrfs/192: use append operator to output log replay results to $seqres.full
Date: Tue, 3 Oct 2023 22:06:33 +0800 [thread overview]
Message-ID: <aad48568-4389-4d2e-fb4d-803fc155366a@oracle.com> (raw)
In-Reply-To: <4569296ec5111e78e4507f3b4ac2d982ac452e83.1696333874.git.fdmanana@suse.com>
On 03/10/2023 19:57, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> 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>
> ---
> tests/btrfs/192 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/btrfs/192 b/tests/btrfs/192
> index 80588a3c..00ea1478 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"
> }
>
next prev parent reply other threads:[~2023-10-03 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 11:57 [PATCH 0/2] fstests: make some tests that use fsstress easier to debug fdmanana
2023-10-03 11:57 ` [PATCH 1/2] fstests: redirect fsstress' stdout to $seqres.full instead of /dev/null fdmanana
2023-10-03 15:24 ` Darrick J. Wong
2023-10-03 11:57 ` [PATCH 2/2] btrfs/192: use append operator to output log replay results to $seqres.full fdmanana
2023-10-03 14:06 ` Anand Jain [this message]
2023-10-04 8:06 ` [PATCH 0/2] fstests: make some tests that use fsstress easier to debug Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aad48568-4389-4d2e-fb4d-803fc155366a@oracle.com \
--to=anand.jain@oracle.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).