From: Eric Sandeen <sandeen@sandeen.net>
To: SCOTT FIELDS <Scott.Fields@kyndryl.com>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: XFS: shrink capability status
Date: Fri, 22 Mar 2024 13:56:46 -0500 [thread overview]
Message-ID: <934595be-7768-4193-9137-d00f183ea712@sandeen.net> (raw)
In-Reply-To: <CY8PR14MB5931A9E3FFDF1984EC556CE48A322@CY8PR14MB5931.namprd14.prod.outlook.com>
On 3/21/24 2:00 PM, SCOTT FIELDS wrote:
>
> Is there any current line item for working to get XFS filesystem shrink capability implemented?
>
> With the basis of the Stratus project (Red Hat's solution to ZFS in many ways) depending on XFS, having the ability to shrink a filesystem is more pressing...imo.
It's actually a bit less pressing, because stratis uses thin
provisioning by default, and so actual disk space behind any
given filesystem is fungible.
That said, the beginnings of shrink are actually already upstream,
but there's still quite a lot of work to be done for it to be
generally useful.
-Eric
> Scott Fields
> Kyndryl
> Senior Lead SRE
>
prev parent reply other threads:[~2024-03-22 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 19:00 XFS: shrink capability status SCOTT FIELDS
2024-03-22 18:56 ` Eric Sandeen [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=934595be-7768-4193-9137-d00f183ea712@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Scott.Fields@kyndryl.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).