From: Eric Sandeen <sandeen@sandeen.net>
To: Spelic <spelic@shiftmail.org>, xfs@oss.sgi.com
Subject: Re: XFS shrinking planned?
Date: Tue, 28 Oct 2014 12:39:13 -0500 [thread overview]
Message-ID: <544FD4C1.4020004@sandeen.net> (raw)
In-Reply-To: <544FC202.1000200@shiftmail.org>
On 10/28/14 11:19 AM, Spelic wrote:
> Hello all,
> XFS is such a good high performance filesystem, kudos for that.
>
> However for large filesystems (which are mainly those that require high performance) the ability to shrink would be really needed. People usually do not have double the space so to move files to a smaller XFS filesystem, and the inability of XFS to shrink forbids major reorganizations of the storage systems.
>
> Currently, for that reason I use ext4. Performance is still decent and flexibility is higher due to the ability to shrink, but I would use XFS if it could shrink.
>
> I suppose shrinking ability is not even planned, is it?
Not formally planned, there are bits and pieces out there (i.e. the inode
mover) which are part of what it might take to achieve a shrinker.
Another option, rather than fs shrinking, is to use the dm-thinp target, which
would allow you to allocate a large-but-sparse block device, create a very
large filesystem on that, and add or remove storage as needed.
(At least I think you can remove it...!)
-Eric
> Thank you
> S.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-28 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 16:19 XFS shrinking planned? Spelic
2014-10-28 17:39 ` Eric Sandeen [this message]
2014-10-29 9:37 ` Spelic
2014-10-29 13:03 ` Eric Sandeen
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=544FD4C1.4020004@sandeen.net \
--to=sandeen@sandeen.net \
--cc=spelic@shiftmail.org \
--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