From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Naohiro Aota <naohiro.aota@wdc.com>
Subject: Re: [PATCH] btrfs: test that fsync on zoned doesn't fail with -EAGAIN
Date: Wed, 11 Nov 2026 07:34:14 -0800 [thread overview]
Message-ID: <avSK9s4cGKqqLpDA@infradead.org> (raw)
In-Reply-To: <20261110095911.2013053-1-johannes.thumshirn@wdc.com>
On Tue, Nov 10, 2026 at 10:59:11AM +0100, Johannes Thumshirn wrote:
> On a zoned filesystem, btrfs_start_transaction() forces a transaction
> commit when the delayed refs reservation exceeds its zoned cap. If the
> cap is still exceeded after the commit, it returned -EAGAIN, which
> fsync passed on to user space.
>
> Run parallel writers creating, overwriting and deleting small files with
> an fsync after every write on a zoned device with a limited number of
> active zones, and check that no fsync fails.
Should this be a generic test?
next prev parent reply other threads:[~2026-11-11 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 9:59 [PATCH] btrfs: test that fsync on zoned doesn't fail with -EAGAIN Johannes Thumshirn
2026-11-11 15:34 ` Christoph Hellwig [this message]
2026-11-13 14:42 ` Johannes Thumshirn
2026-11-14 16:02 ` Zorro Lang
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=avSK9s4cGKqqLpDA@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--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