From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Naohiro Aota <naohiro.aota@wdc.com>, linux-btrfs@vger.kernel.org
Subject: Re: zbd/009 (btrfs on zone gaps) fail on current Linus tree
Date: Wed, 15 Oct 2025 23:59:27 -0700 [thread overview]
Message-ID: <aPCXz7ktsyE8BLeG@infradead.org> (raw)
In-Reply-To: <a2c698cf-5735-4ef4-859b-057fece29c9d@wdc.com>
I've bisected the hang to:
commit 04147d8394e80acaaebf0365f112339e8b606c05 (HEAD)
Author: Naohiro Aota <naohiro.aota@wdc.com>
Date: Wed Jul 16 16:59:55 2025 +0900
btrfs: zoned: limit active zones to max_open_zones
with that patch zbd/009 hangs 100% for my config, and without it,
it works fine 100%.
On Wed, Oct 08, 2025 at 02:09:00PM +0000, Johannes Thumshirn wrote:
> On 10/8/25 8:07 AM, Johannes Thumshirn wrote:
> > On 10/8/25 8:02 AM, hch@infradead.org wrote:
> >> On Tue, Oct 07, 2025 at 11:16:08AM +0000, Johannes Thumshirn wrote:
> >>> hmm how reproducible is it on your side? I cannot reproduce it (yet)
> >> 100% over about a dozen runs, a few of those including unrelated
> >> patches.
> >>
> >> My kernel .config and qemu command line are attached.
> >>
> > OK I'll give it a shot. For my config + qemu it survived 250 runs of
> > zbd/009 yesterday without a hang :(
> >
> >
> Nope, even with your kconfig no success on recreating the bug.
>
---end quoted text---
next prev parent reply other threads:[~2025-10-16 6:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 6:21 zbd/009 (btrfs on zone gaps) fail on current Linus tree Christoph Hellwig
2025-10-07 11:16 ` Johannes Thumshirn
2025-10-08 6:02 ` hch
2025-10-08 6:06 ` Johannes Thumshirn
2025-10-08 14:09 ` Johannes Thumshirn
2025-10-10 5:25 ` hch
2025-10-16 6:59 ` Christoph Hellwig [this message]
2025-10-17 13:33 ` Johannes Thumshirn
2025-10-20 6:47 ` hch
2025-10-20 6:52 ` Johannes Thumshirn
2025-10-20 6:53 ` hch
2025-10-20 6:55 ` Johannes Thumshirn
2025-10-20 7:21 ` hch
2025-10-20 7:43 ` Johannes Thumshirn
2025-10-20 9:03 ` Naohiro Aota
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=aPCXz7ktsyE8BLeG@infradead.org \
--to=hch@infradead.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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