From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Марк Коренберг" <socketpair@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: [RFE] xfs_growfs: option to clamp growth to an AG boundary
Date: Tue, 24 Feb 2026 11:49:04 -0800 [thread overview]
Message-ID: <20260224194904.GC13843@frogsfrogsfrogs> (raw)
In-Reply-To: <aZ29iJJF9sGfya1k@infradead.org>
On Tue, Feb 24, 2026 at 07:02:32AM -0800, Christoph Hellwig wrote:
> On Mon, Feb 23, 2026 at 02:48:48PM +0500, Марк Коренберг wrote:
> > This feels like something xfsprogs could support directly. My proposals:
>
> I like your proposal. This is actually a relatively east project,
> and I've happy to mentor whomever wants to take it up. Although
> I think json output while generally useful is probably a separate
> issue and should be addressed separately and in a more general
> fashion.
I've long thought it might be useful to have an xfs_db command that
could spit out a mkfs config file for a given filesystem, so you could
just do:
# xfs_db -c 'mkfs_config' /dev/sda1 > /tmp/foo.cfg
# mkfs.xfs -c /tmp/foo.cfg -f /dev/sdb1
and then sdb1 gets whatever featureset sda1 had. The reason I never
pursued this is that I don't know how much we'd really want to preserve.
User-visible features, yes. But what about geometry things like group
size, volume size, or RAID stripe parameters?
--D
next prev parent reply other threads:[~2026-02-24 19:49 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
2026-02-24 15:02 ` Christoph Hellwig
2026-02-24 19:49 ` Darrick J. Wong [this message]
-- 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=20260224194904.GC13843@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=hch@infradead.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