From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: any chance for xfs shrinking?
Date: Tue, 12 May 2015 07:35:22 -0500 [thread overview]
Message-ID: <5551F38A.2050102@sandeen.net> (raw)
In-Reply-To: <5551EBB2.9010508@profihost.ag>
On 5/12/15 7:01 AM, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> while cloud / vms usage become more and more popular and qemu now also
> offers memory hot add and unplug, cpu hot add and unplug, we still
> suffer from a missing xfs shrink.
Filesystem shrink is a very different scenario than "cloud / vms" needs
for hot memory & cpu plugging, IMHO.
> I would like to continue to use XFS as it is a rock solid base since
> around 10 years for us.
>
> But one missing piece in variable ressource usage for us is disk
> shrinking. Is there any chance to get an xfs online shrinking?
Under what circumstance does your workflow require a filesystem shrink?
Honest question, I'm not challenging you, but I would like to understand
what it is about shrink that is so critical it may cause you to stop using
XFS.
One thing about shrink - while i.e. ext4 supports it, the end result of
a shrunk filesystem is a scrambled filesystem. All those heuristics that
made the filesystem reasonably performant as it aged get thrown out the
window as the fs scavenges for space into which to shrink the filesystem...
That said, another option is to use the dm-thinp target, and allocate /
de-allocate storage resources to the underlying block device as needed.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-05-12 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 12:01 any chance for xfs shrinking? Stefan Priebe - Profihost AG
2015-05-12 12:27 ` Dewangga Bachrul Alam
2015-05-12 12:35 ` Eric Sandeen [this message]
2015-05-12 12:41 ` Stefan Priebe - Profihost AG
2015-05-12 18:22 ` Andrey Korolyov
2015-05-13 1:27 ` greg.freemyer
2015-05-12 22:15 ` Dave Chinner
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=5551F38A.2050102@sandeen.net \
--to=sandeen@sandeen.net \
--cc=s.priebe@profihost.ag \
--cc=xfs@oss.sgi.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