From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Tarik Ceylan <Tarik.Ceylan@ruhr-uni-bochum.de>,
linux-xfs@vger.kernel.org
Subject: Re: How to reliably measure fs usage with reflinks enabled?
Date: Tue, 15 May 2018 08:57:51 +1000 [thread overview]
Message-ID: <20180514225751.GB10363@dastard> (raw)
In-Reply-To: <866a5e96-e900-d330-0efb-6413f85f86a3@sandeen.net>
On Mon, May 14, 2018 at 05:02:53PM -0500, Eric Sandeen wrote:
>
>
> On 5/14/18 3:02 PM, Tarik Ceylan wrote:
> > How can one reliably measure filesystem usage on partitions that were compiled with -m reflink=1 ?
> > Here are some numbers i am measuring with df -h (on different partitions holding the same data):
> > 7.7G of 36G (-b size=512 -m crc=0 )
> > 8.6G of 36G (-b size=4096 -m crc=1 )
>
> 8x larger inodes will take 8x more space, but you didn't say how many
> inodes you have allocated.
>
> > 11G of 36G (-b size=1024 -m crc=1,reflink=1,rmapbt=1 -i sparse=1 )
> > 32G of 864G (-b size=4096 -m crc=1,reflink=1 )
>
> In that last case, you have a wildly different total fs size, so probably
> no fair comparison here either.
>
> The reverse mapping btree also takes up space. You're turning too many
> knobs at once. ;)
Also, we reserve a lot of space for reflink/rmapbt metadata that
isn't actually used, so you're not actually using any more space
than the "-b size=4096 -m crc=1" case. I have plans for hiding that
reservation from users so that we don't get questions like this....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-05-14 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 20:02 How to reliably measure fs usage with reflinks enabled? Tarik Ceylan
2018-05-14 22:02 ` Eric Sandeen
2018-05-14 22:57 ` Dave Chinner [this message]
2018-05-14 23:37 ` Tarik Ceylan
2018-05-15 1:29 ` Dave Chinner
2018-05-15 13:52 ` Mike Fleetwood
2018-05-16 0:13 ` Dave Chinner
2018-05-18 14:43 ` Mike Fleetwood
2018-05-18 14:56 ` Eric Sandeen
2018-05-19 8:36 ` Mike Fleetwood
2018-05-18 14:58 ` Darrick J. Wong
2018-05-20 0:10 ` 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=20180514225751.GB10363@dastard \
--to=david@fromorbit.com \
--cc=Tarik.Ceylan@ruhr-uni-bochum.de \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.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