From: "hch@infradead.org" <hch@infradead.org>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: "hch@infradead.org" <hch@infradead.org>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: zbd/009 (btrfs on zone gaps) fail on current Linus tree
Date: Mon, 20 Oct 2025 00:21:56 -0700 [thread overview]
Message-ID: <aPXjFL6vz6UM_CH5@infradead.org> (raw)
In-Reply-To: <0f067fa8-acaf-400f-a36c-e124ae95e337@wdc.com>
On Mon, Oct 20, 2025 at 06:55:46AM +0000, Johannes Thumshirn wrote:
> On 10/20/25 8:53 AM, hch@infradead.org wrote:
> > On Mon, Oct 20, 2025 at 06:52:04AM +0000, Johannes Thumshirn wrote:
> >> OK, maybe I tested wrong. Does it also hang if you only run zbd/009 or
> >> do you need to run the other zbd tests before?
> > Just running zbd/009 is fine.
> >
> > Also make sure to try to use my kvm script as-is as it gets, given
> > the bisected commit I might be sensitive to the open zone limits or
> > zone append size or something like that.
>
> Yeah the issue on my side could be that I don't have virtio-blk devices
> attached to the VM as I don't have debian images lying aroudn for the
> rootfs (I'm using my hosts' root as a RO virtiofs mount).
Actually, the zbd tests emulate the zoned devices on top of the regular
ones, so it should not matter. Here is my blktests config, btw:
TEST_DEVS=(/dev/vdb)
nvme_trtype=loop
so nothing special.
next prev parent reply other threads:[~2025-10-20 7:21 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
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 [this message]
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=aPXjFL6vz6UM_CH5@infradead.org \
--to=hch@infradead.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=linux-btrfs@vger.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