Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Zorro Lang <zlang@redhat.com>,
	fstests@vger.kernel.org,  linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/5] generic/746: skip on zoned btrfs
Date: Mon, 27 Jul 2026 11:00:35 +0200	[thread overview]
Message-ID: <amcdDtFZ5pYz-nI0@neo> (raw)
In-Reply-To: <al5c4krF3A03HZ1o@infradead.org>

On Mon, Jul 20, 2026 at 10:37:38AM -0700, Christoph Hellwig wrote:
> On Mon, Jul 20, 2026 at 01:18:47PM +0200, Johannes Thumshirn wrote:
> > The test relies on loop device discards punching holes in the backing
> > image file (holes are then detected via fiemap on the backing file).
> > Zoned btrfs does not support fallocate/punch hole, so fstrim on the
> > loop device cannot free space in the backing file and the test cannot
> > work.
> > 
> > Skip the test on zoned devices, but only for btrfs so that other
> > filesystems (e.g. zoned XFS/f2fs) can still run it.
> 
> This should use feature detection and not hard code file systems.

I didn't find anything for that. Only using _require_xfs_io_command
"fpunch", but the test is not using ot so it felt wrong. 

> 
> I'm also a bit surprised that zoned btrfs doesn't support hole
> punches.  Unlike classic unwritten extents there is nothing in a
> zone model preventing them from working.  Did you try just enabling
> hole punches in btrfs?
>

It is not the zoned device model that prevents us but a desciccion we
did in zoned BTRFS when doing the initial support for it. I can look
into hole punching but I got a lot of other more urgent fires to put out
and features people are waiting for first.

  reply	other threads:[~2026-07-27  9:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 11:18 [PATCH 0/5] fstests: misc fixes for zoned btrfs Johannes Thumshirn
2026-07-20 11:18 ` [PATCH 1/5] common/btrfs: fix awk field separator in _check_temp_fsid Johannes Thumshirn
2026-07-20 16:44   ` Filipe Manana
2026-07-21  6:43     ` Johannes Thumshirn
2026-07-20 11:18 ` [PATCH 2/5] btrfs/199: skip on zoned devices Johannes Thumshirn
2026-07-20 11:18 ` [PATCH 3/5] generic/746: skip on zoned btrfs Johannes Thumshirn
2026-07-20 17:37   ` Christoph Hellwig
2026-07-27  9:00     ` Johannes Thumshirn [this message]
2026-07-20 11:18 ` [PATCH 4/5] btrfs/284: skip on zoned devices Johannes Thumshirn
2026-07-20 11:18 ` [PATCH 5/5] generic/781: fix copyright Johannes Thumshirn

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=amcdDtFZ5pYz-nI0@neo \
    --to=johannes.thumshirn@wdc.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@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