From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: zlang@kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] common: log mkfs output in _test_streams
Date: Tue, 30 Jun 2026 12:13:03 -0700 [thread overview]
Message-ID: <20260630191303.GA6517@frogsfrogsfrogs> (raw)
In-Reply-To: <20260630142047.3612436-1-hch@lst.de>
On Tue, Jun 30, 2026 at 08:20:47AM -0600, Christoph Hellwig wrote:
> Log the mkfs output to allow debugging the mkfs paramters,
> especially when mkfs and thus the test fails.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> common/filestreams | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/common/filestreams b/common/filestreams
> index 459de8c6b6a6..0b11b6644977 100644
> --- a/common/filestreams
> +++ b/common/filestreams
> @@ -89,7 +89,7 @@ _test_streams() {
> # Skip these tests on zoned file systems as filestreams don't work
> # with the zoned allocator, and the operation below would force it into
> # the tiny data section only used for metadata anyway.
> - _try_scratch_mkfs_xfs >/dev/null 2>&1 || _fail "mkfs failed"
> + _try_scratch_mkfs_xfs >$seqres.full 2>&1 || _fail "mkfs failed"
This should >>$seqres.full so that you don't obliterate whatever might
already be in that file. Otherwise this sounds like a good idea to me.
--D
> _scratch_mount
> _require_xfs_scratch_non_zoned
> _scratch_unmount 2>/dev/null
> --
> 2.53.0
>
>
next prev parent reply other threads:[~2026-06-30 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 14:20 [PATCH] common: log mkfs output in _test_streams Christoph Hellwig
2026-06-30 19:13 ` Darrick J. Wong [this message]
2026-07-01 10:50 ` Christoph Hellwig
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=20260630191303.GA6517@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=zlang@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