From: "Darrick J. Wong" <djwong@kernel.org>
To: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>, linux-xfs@vger.kernel.org
Subject: Re: Shrinking XFS - is that happening?
Date: Mon, 12 Jan 2026 13:53:28 -0800 [thread overview]
Message-ID: <20260112215328.GF15551@frogsfrogsfrogs> (raw)
In-Reply-To: <2f9c2c7d-a6c1-4f79-b7e5-6bc369bb585b@gmail.com>
On Mon, Jan 12, 2026 at 08:05:12PM +0530, Nirjhar Roy (IBM) wrote:
>
> On 8/11/25 20:55, Darrick J. Wong wrote:
> > 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/
>
> Hi Darrick,
>
> I am working on the extending my online shrink fs work [1] to realtime fs
> shrink and as a part of that project, I am looking into the patchbomb above
> - specifically " [PATCHSET 3/5] xfsprogs: defragment free space". I have a
> high level questions before I delve deep into the patches above:
>
> 1. Can you please elaborate a bit on what do you mean by "finish the
> evacuation part"? I took a very high level look at the patch, and it seems
> it is already adding support to move data from one rtg/AG to another?
It can evacuate fully mapped blocks, but it can't do that for the EOF
block if the EOF is in the middle of that block.
--D
> --NR
>
> >
> > --D
>
> --
> Nirjhar Roy
> Linux Kernel Developer
> IBM, Bangalore
>
>
next prev parent reply other threads:[~2026-01-12 21:53 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
2026-01-12 14:35 ` Nirjhar Roy (IBM)
2026-01-12 21:53 ` Darrick J. Wong [this message]
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=20260112215328.GF15551@frogsfrogsfrogs \
--to=djwong@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox