From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "Christoph Hellwig" <hch@infradead.org>,
"Марк Коренберг" <socketpair@gmail.com>,
linux-xfs@vger.kernel.org
Subject: Re: [RFE] xfs_growfs: option to clamp growth to an AG boundary
Date: Wed, 25 Feb 2026 06:21:53 -0800 [thread overview]
Message-ID: <aZ8FgX6oF5MYEROL@infradead.org> (raw)
In-Reply-To: <20260224222551.GA13853@frogsfrogsfrogs>
On Tue, Feb 24, 2026 at 02:25:51PM -0800, Darrick J. Wong wrote:
> > Yeah, I'll give that a spin.
>
> ...and that regresses generic/33[34] because they actually fill the
> filesystem up to full (or at least to the point where the fs won't let
> us write more) and test that reflink returns ENOSPC.
>
> Seeing as the reporter would actually rather we didn't fall back to a
> slow pagecache copy(!) I'll drop this patch.
Not sure if the reported wanted it, but randomly failing reflink with
ENOSPC on a file system that is not out of space is really, really
weird behavior, and I think we should fix it.
next prev parent reply other threads:[~2026-02-25 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 9:48 [RFE] xfs_growfs: option to clamp growth to an AG boundary Марк Коренберг
2026-02-23 16:23 ` Darrick J. Wong
2026-02-23 19:29 ` Марк Коренберг
2026-02-23 23:08 ` Darrick J. Wong
2026-02-24 6:17 ` Марк Коренберг
2026-02-24 15:01 ` Christoph Hellwig
2026-02-24 19:44 ` Darrick J. Wong
2026-02-24 22:25 ` Darrick J. Wong
2026-02-25 14:21 ` Christoph Hellwig [this message]
2026-02-24 15:02 ` Christoph Hellwig
2026-02-24 19:49 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2026-02-25 8:21 Lukas Herbolt
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=aZ8FgX6oF5MYEROL@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=socketpair@gmail.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