From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Hans Holmberg <hans.holmberg@wdc.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: [PATCH 1/4] xfs: check for zoned-specific errors in _try_scratch_mkfs_xfs
Date: Thu, 1 May 2025 08:38:55 -0500 [thread overview]
Message-ID: <20250501133900.2880958-2-hch@lst.de> (raw)
In-Reply-To: <20250501133900.2880958-1-hch@lst.de>
Check for a few errors issued for unsupported zoned configurations in
_try_scratch_mkfs_xfs so that the test is not run instead of failed.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
common/xfs | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/common/xfs b/common/xfs
index 96c15f3c7bb0..39650bac6c23 100644
--- a/common/xfs
+++ b/common/xfs
@@ -160,6 +160,11 @@ _try_scratch_mkfs_xfs()
grep -q crc=0 $tmp.mkfsstd && _force_xfsv4_mount_options
+ grep -q "zoned file systems do not support" $tmp.mkfserr && \
+ _notrun "Not supported on zoned file systems"
+ grep -q "must be greater than the minimum zone count" $tmp.mkfserr && \
+ _notrun "Zone count too small"
+
if [ $mkfs_status -eq 0 -a "$LARGE_SCRATCH_DEV" = yes ]; then
# manually parse the mkfs output to get the fs size in bytes
local fs_size
--
2.47.2
next prev parent reply other threads:[~2025-05-01 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 13:38 finishe xfstests support for zoned XFS Christoph Hellwig
2025-05-01 13:38 ` Christoph Hellwig [this message]
2025-05-01 13:38 ` [PATCH 2/4] common: notrun in mkfs_dev for too small zoned file systems Christoph Hellwig
2025-05-01 13:38 ` [PATCH 3/4] common: support internal RT device in _require_realtime Christoph Hellwig
2025-05-01 13:38 ` [PATCH 4/4] common: support internal RT devices in scratch_mkfs_sized Christoph Hellwig
2025-05-01 15:02 ` finishe xfstests support for zoned XFS Darrick J. Wong
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=20250501133900.2880958-2-hch@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=linux-xfs@vger.kernel.org \
--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