Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Xavier Claude <contact@xavierclaude.be>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH xfsprogs] Document current limitation of shrinking fs
Date: Mon, 18 Aug 2025 13:46:00 -0700	[thread overview]
Message-ID: <20250818204600.GW7965@frogsfrogsfrogs> (raw)
In-Reply-To: <20250818151858.83521-1-contact@xavierclaude.be>

On Mon, Aug 18, 2025 at 03:19:10PM +0000, Xavier Claude wrote:
> Hello,
> 
> If I understand the code correctly[1], shrinking more than one AG is not
> supported. So I propose to add it to the manpage, like for the log
> shrinking option.
> 
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/xfs/xfs_fsops.c?h=v6.17-rc2#n152
> -- >8 --
> 
> Current implementation in the kernel doesn't allow to shrink more that
> one AG
> 
> Signed-off-by: Xavier Claude <contact@xavierclaude.be>
> ---
>  man/man8/xfs_growfs.8 | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/man/man8/xfs_growfs.8 b/man/man8/xfs_growfs.8
> index a0126927..2e329fa6 100644
> --- a/man/man8/xfs_growfs.8
> +++ b/man/man8/xfs_growfs.8
> @@ -70,6 +70,7 @@ otherwise the data section is grown to the largest size possible with the
>  option. The size is expressed in filesystem blocks. A filesystem with only
>  1 AG cannot be shrunk further, and a filesystem cannot be shrunk to the point
>  where it would only have 1 AG.
> +.B [NOTE: Only shrinking the last AG without removing it is implemented]

That's my understanding of where growfs is right now wrt shrinking

Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

>  .TP
>  .B \-e
>  Allows the real-time extent size to be specified. In
> -- 
> 2.50.1
> 
> 
> 

      reply	other threads:[~2025-08-18 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 15:19 [PATCH xfsprogs] Document current limitation of shrinking fs Xavier Claude
2025-08-18 20:46 ` Darrick J. Wong [this message]

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=20250818204600.GW7965@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=contact@xavierclaude.be \
    --cc=linux-xfs@vger.kernel.org \
    /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