On 5/12/15 7:01 AM, Stefan Priebe - Profihost AG wrote:
> 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
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.