public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Zorro Lang <zlang@redhat.com>,
	Naohiro Aota <naohiro.aota@wdc.com>,
	fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3] fstests: test premature ENOSPC in zoned garbage collection
Date: Wed, 15 Apr 2026 07:22:03 +0200	[thread overview]
Message-ID: <20260415052203.GB26443@lst.de> (raw)
In-Reply-To: <20260414143341.167875-1-johannes.thumshirn@wdc.com>

On Tue, Apr 14, 2026 at 04:33:41PM +0200, Johannes Thumshirn wrote:
> This test stresses garbage collection in zoned file systems by
> constantly overwriting the same file. It is inspired by a reproducer for
> a btrfs bugifx.

s/bugifx/bugfix/

I tried this on XFS, and it doesn't work as XFS uses SCRATCH_RTDEV for
zoned data.  Manually hacking in SCRATCH_RTDEV makes it work, but that
will break btrfs.  Maybe you can add a little:

if [ -b "$SCRATCH_RTDEV" ];
	zoned_dev=$SCRATCH_RTDEV
else
	zoned_dev=$SCRATCH_DEV
endif

end then use $zoned_dev to make it portable?

I also tried it on f2fs, but mkfs.f2fs fails now with a 'different sector
sizes' warning when using a 4k-sector conventional and 4k-sector zoned
ZNS namespace, so I guess I'll give up on that.

  reply	other threads:[~2026-04-15  5:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 14:33 [PATCH v3] fstests: test premature ENOSPC in zoned garbage collection Johannes Thumshirn
2026-04-15  5:22 ` Christoph Hellwig [this message]
2026-04-15  5:53   ` Johannes Thumshirn
2026-04-15  5:56     ` Christoph Hellwig
2026-04-15  6:10       ` Johannes Thumshirn
2026-04-15  6:27         ` Christoph Hellwig
2026-04-15  6:53           ` Johannes Thumshirn
2026-04-15  7:04             ` Christoph Hellwig

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=20260415052203.GB26443@lst.de \
    --to=hch@lst.de \
    --cc=fstests@vger.kernel.org \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --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