linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Carlos Maiolino <cem@kernel.org>
Cc: Zorro Lang <zlang@redhat.com>, 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>
Subject: Re: [PATCH] generic: basic smoke for filesystems on zoned block devices
Date: Tue, 7 Oct 2025 06:20:42 +0000	[thread overview]
Message-ID: <78e121bd-8f6c-4b79-808c-9f5f75c90d8c@wdc.com> (raw)
In-Reply-To: <iqwkuhobfvpeiktvk6pba6ahirgzngltj3ilrifcfgaugme67s@r54pl6d6foys>

On 10/6/25 8:40 PM, Carlos Maiolino wrote:
> On Mon, Oct 06, 2025 at 03:24:55PM +0200, Johannes Thumshirn wrote:
>> Add a basic smoke test for filesystems that support running on zoned
>> block devices.
>>
>> It creates a zloop device with 2 sequential and 62 sequential zones,
> This seems wrong? Don't you mean 2 conventional zones?
> Also, won't the arguments used to create the zone dev end up creating 64
> sequential zones? I might be very wrong here, so my apologies in advance
> but looking into the zloop code this seems that 256MiB zone size will end
> up creating 64 sequential zones instead of 62?

2 conventional zones and 62 sequential zones, my mistake:

root@virtme-ng:/mnt# echo "$zloop_args" > /dev/zloop-control
[   75.986238] zloop: Added device 0: 64 zones of 256 MB, 4096 B block size
root@virtme-ng:/mnt# ls $zloopdir/0
cnv-000000  seq-000011  seq-000022  seq-000033  seq-000044 seq-000055
cnv-000001  seq-000012  seq-000023  seq-000034  seq-000045 seq-000056
seq-000002  seq-000013  seq-000024  seq-000035  seq-000046 seq-000057
seq-000003  seq-000014  seq-000025  seq-000036  seq-000047 seq-000058
seq-000004  seq-000015  seq-000026  seq-000037  seq-000048 seq-000059
seq-000005  seq-000016  seq-000027  seq-000038  seq-000049 seq-000060
seq-000006  seq-000017  seq-000028  seq-000039  seq-000050 seq-000061
seq-000007  seq-000018  seq-000029  seq-000040  seq-000051 seq-000062
seq-000008  seq-000019  seq-000030  seq-000041  seq-000052 seq-000063
seq-000009  seq-000020  seq-000031  seq-000042  seq-000053
seq-000010  seq-000021  seq-000032  seq-000043  seq-000054



  reply	other threads:[~2025-10-07  6:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 13:24 [PATCH 0/2] fstests: basic smoke test on zoned loop device Johannes Thumshirn
2025-10-06 13:24 ` [PATCH 1/2] common/zoned: add _require_zloop Johannes Thumshirn
2025-10-06 18:06   ` Carlos Maiolino
2025-10-07  4:13   ` Christoph Hellwig
2025-10-06 13:24 ` [PATCH] generic: basic smoke for filesystems on zoned block devices Johannes Thumshirn
2025-10-06 18:40   ` Carlos Maiolino
2025-10-07  6:20     ` Johannes Thumshirn [this message]
2025-10-07  7:54       ` Carlos Maiolino
2025-10-07  4:15   ` Christoph Hellwig
2025-10-17 14:57   ` Zorro Lang
2025-10-17 18:21     ` Zorro Lang
2025-10-07  4:15 ` [PATCH 0/2] fstests: basic smoke test on zoned loop device 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=78e121bd-8f6c-4b79-808c-9f5f75c90d8c@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=Hans.Holmberg@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=cem@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;
as well as URLs for NNTP newsgroup(s).