All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	linux-xfs@vger.kernel.org
Subject: Re: Shrinking XFS - is that happening?
Date: Mon, 11 Aug 2025 08:25:32 -0700	[thread overview]
Message-ID: <20250811152532.GH7965@frogsfrogsfrogs> (raw)
In-Reply-To: <aJnKcktFW6jPBETP@infradead.org>

On Mon, Aug 11, 2025 at 03:48:18AM -0700, Christoph Hellwig wrote:
> On Tue, Aug 05, 2025 at 10:20:15AM +0530, Nirjhar Roy (IBM) wrote:
> > On Mon, 2025-08-04 at 17:13 +0200, Roy Sigurd Karlsbakk wrote:
> > > Hi all!
> > > 
> > > I beleive I heard something from someone some time back about work in progress on shrinking xfs filesystems. Is this something that's been worked with or have I been lied to or just had a nice dream?
> > > 
> > > roy
> > I have recently posted an RFC[1]. The work is based/inspired from an old RFC[2] by Gao and ideas
> > given by Dave Chinner.
> 
> Like the previous attempts it doesn't seem to include an attempt to
> address the elephant in the room:  moving inodes out of the to be
> removed AGs or tail blocks of an AG.

Anyone who wants to finish the evacuation part is welcome to pick this
up:
https://lore.kernel.org/linux-xfs/173568777852.2709794.6356870909327619205.stgit@frogsfrogsfrogs/

--D

  reply	other threads:[~2025-08-11 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 15:13 Shrinking XFS - is that happening? Roy Sigurd Karlsbakk
2025-08-05  4:50 ` Nirjhar Roy (IBM)
2025-08-11 10:48   ` Christoph Hellwig
2025-08-11 15:25     ` Darrick J. Wong [this message]
2026-01-12 14:35       ` Nirjhar Roy (IBM)
2026-01-12 21:53         ` Darrick J. Wong
2025-08-05  5:01 ` Nirjhar Roy (IBM)

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=20250811152532.GH7965@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nirjhar.roy.lists@gmail.com \
    --cc=roy@karlsbakk.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.