From: Dave Chinner <david@fromorbit.com>
To: Danny Shavit <danny@zadarastorage.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs metadata overhead
Date: Sat, 25 Jun 2016 08:51:45 +1000 [thread overview]
Message-ID: <20160624225145.GF12670@dastard> (raw)
In-Reply-To: <CAC=x_0g_iktOKOKiRF5Ku7N-PSbCXOR+Amhm577YjNYQaRPjeA@mail.gmail.com>
On Fri, Jun 24, 2016 at 04:21:39PM +0300, Danny Shavit wrote:
> I see.
> So using bulk_stat ioctl in similar way to xfs_fsr and summing allocated
> size will result with more accurate number?
No. du includes *directory blocks* in it's sum. bulkstat only counts
inodes, which is not counted by du and is part of the metadata you
have already accounted for. Even then, bulkstat doesn't give an
accurate account o space used by inodes because they can be sparsely
allocated from within inode chunks.
Just snapshot the volume, run metadump on the snapshot - it's the
fastest, most reliable way to work out how much metadata is in a
filesystem right now...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-06-24 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:58 xfs metadata overhead Danny Shavit
2016-06-22 22:51 ` Dave Chinner
2016-06-23 15:04 ` Danny Shavit
2016-06-23 18:12 ` Eric Sandeen
[not found] ` <CAC=x_0hnGQHAenv985+FusWxK_63AatB_XK_mqbAmyt=OxqYrg@mail.gmail.com>
2016-06-24 13:17 ` Eric Sandeen
2016-06-24 13:21 ` Danny Shavit
2016-06-24 22:51 ` Dave Chinner [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=20160624225145.GF12670@dastard \
--to=david@fromorbit.com \
--cc=danny@zadarastorage.com \
--cc=sandeen@sandeen.net \
--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