Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Lukas Herbolt <lukas@herbolt.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: socketpair@gmail.com, Linux Xfs <linux-xfs@vger.kernel.org>
Subject: [RFE] xfs_growfs: option to clamp growth to an AG boundary
Date: Wed, 25 Feb 2026 09:21:42 +0100	[thread overview]
Message-ID: <74e545ca6c3b98c00018f604812853cc@herbolt.com> (raw)

> 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 like the idea and can take a look at it, but I will leave it to
the author if they will pick it up.

Just for the LVM extent size, LVM does not expose it unless you look
at the metadata, afaik.

> I think json output while generally useful is probably a separate
> issue and should be addressed separately and in a more general
> fashion.

I guess json output could be also added to mkfs.xfs, xfs_admin (xfs_db)


-- 
-lhe

             reply	other threads:[~2026-02-25  8:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  8:21 Lukas Herbolt [this message]
  -- strict thread matches above, loose matches on Subject: below --
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

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=74e545ca6c3b98c00018f604812853cc@herbolt.com \
    --to=lukas@herbolt.com \
    --cc=aZ29iJJF9sGfya1k@infradead.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