From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, djwong@kernel.org, dlemoal@kernel.org,
hans.holmberg@wdc.com, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: add a test for number of open zones on conventional devices
Date: Tue, 7 Apr 2026 08:27:07 +0200 [thread overview]
Message-ID: <20260407062707.GA6937@lst.de> (raw)
In-Reply-To: <20260406170528.sxcm3qcndjhwm7pp@doltdoltdolt>
On Tue, Apr 07, 2026 at 01:05:28AM +0800, Zorro Lang wrote:
> >
> > I think _notrun if mkfs or the initial mount fails might be easier and
> > better here.
>
> How about a _require_xfs_mkfs_zoned ?
>
> And about `_scratch_mount -o max_open_zones=${open_zones}`, if max_open_zones
> mount option isn't supported, _scratch_mount will fail directly. So how about
>
> _try_scratch_mount -o max_open_zones=${open_zones} || \
> _notrun "max_open_zones option is not supported"
>
> Or we can have a helper for that, as xfs/642~644 and xfs/668 also need that.
I'll take a look. max_open_zones is always supported for zoned xfs
file systems - the notrun is intended to cover the case where the kernel
can't mount zoned file systems - either because it is too old, or because
XFS_RT is not enabled.
prev parent reply other threads:[~2026-04-07 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 15:23 [PATCH v2] xfs: add a test for number of open zones on conventional devices Christoph Hellwig
2026-03-31 19:40 ` Damien Le Moal
2026-03-31 21:18 ` Zorro Lang
2026-04-01 6:18 ` Christoph Hellwig
2026-04-01 7:59 ` Zorro Lang
2026-04-01 14:06 ` Christoph Hellwig
2026-04-06 17:05 ` Zorro Lang
2026-04-07 6:27 ` Christoph Hellwig [this message]
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=20260407062707.GA6937@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.