From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, djwong@kernel.org, hans.holmberg@wdc.com,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: add a test for number of open zones on conventional devices
Date: Tue, 31 Mar 2026 17:15:14 +0200 [thread overview]
Message-ID: <20260331151514.GA7927@lst.de> (raw)
In-Reply-To: <26debf2c-7b0c-49bc-b2e6-fc9eb3d8bde0@kernel.org>
On Tue, Mar 31, 2026 at 07:00:39PM +0900, Damien Le Moal wrote:
> Hmmm. I think you should delete odd numbered files only since they are going to
> be written at the end of a zone. Otherwise, you make the zone empty, and it will
> thus not be considered as open.
Yes, but due to the unevent number I did reproduce the bug even
with this version. I tried your loop and this overshoots the open
zone limit even more without the fix, so I'll switch to that.
prev parent reply other threads:[~2026-03-31 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 13:00 [PATCH] xfs: add a test for number of open zones on conventional devices Christoph Hellwig
2026-03-31 10:00 ` Damien Le Moal
2026-03-31 15:15 ` 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=20260331151514.GA7927@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 \
/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