From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Anand Jain <anajain.sg@gmail.com>, Zorro Lang <zlang@redhat.com>
Cc: hch <hch@lst.de>, Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Hans Holmberg <Hans.Holmberg@wdc.com>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [PATCH v3 3/3] generic: basic smoke for filesystems on zoned block devices
Date: Mon, 13 Oct 2025 14:06:06 +0000 [thread overview]
Message-ID: <4eeb481f-b94d-4c2f-909e-7c29ac2440b2@wdc.com> (raw)
In-Reply-To: <006ae40b-b2e6-441a-b2d3-296d1e166787@gmail.com>
On 10/13/25 3:55 PM, Anand Jain wrote:
> Johannes,
>
> The test case is failing with XFS. For some reason, the mkfs error
> wasn't captured in the output, so I had to modify the test slightly.
> Errors and the diff is below.
>
> Thanks, Anand
>
> -------
> SECTION -- generic-config
> RECREATING -- xfs on /dev/sde
> FSTYP -- xfs (non-debug)
> PLATFORM -- Linux/x86_64 feddev 6.16.10-100.fc41.x86_64 #1 SMP
> PREEMPT_DYNAMIC Thu Oct 2 18:19:14 UTC 2025
> MKFS_OPTIONS -- -f /dev/sda
> MOUNT_OPTIONS -- /dev/sda /mnt/scratch
>
> generic/772 [not run] cannot mkfs zoned filesystem
> Ran: generic/772
> Not run: generic/772
> Passed all 1 tests
Hi Anand,
Looking at the output it isn't failing but skipped on your XFS config.
This is expected if XFS isn't build with support for the zoned realtime
device. I've been discussing this with Christoph, because for XFS there
is no feature flag in sysfs we can check if the kernel can actually
support a zoned RT device (unlike f2fs or btrfs which do have this in
sysfs).
Christoph's idea was to do exactly this, if no zoned RT support is
compiled in the kernel. Hence the _try_mkfs_dev instead of a plain
_mkfs_dev call.
So I /think/ you just validated that the skip if !CONFIG_BLK_DEV_ZONED
&& !CONFIG_XFS_RT check works.
Thanks,
Johannes
next prev parent reply other threads:[~2025-10-13 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 8:07 [PATCH v3 0/3] fstests: basic smoke test on zoned loop device Johannes Thumshirn
2025-10-13 8:07 ` [PATCH v3 1/3] common/zoned: add _require_zloop Johannes Thumshirn
2025-10-13 8:43 ` Naohiro Aota
2025-10-14 4:33 ` Christoph Hellwig
2025-10-13 8:07 ` [PATCH v3 2/3] common/zoned: add _create_zloop Johannes Thumshirn
2025-10-14 9:04 ` Naohiro Aota
2025-10-13 8:07 ` [PATCH v3 3/3] generic: basic smoke for filesystems on zoned block devices Johannes Thumshirn
2025-10-13 13:55 ` Anand Jain
2025-10-13 14:06 ` Johannes Thumshirn [this message]
2025-10-13 14:42 ` Anand Jain
2025-10-14 4:30 ` hch
2025-10-14 14:38 ` Anand Jain
2025-10-15 4:09 ` hch
2025-10-14 4:33 ` 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=4eeb481f-b94d-4c2f-909e-7c29ac2440b2@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Hans.Holmberg@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=anajain.sg@gmail.com \
--cc=cem@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-xfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox