xfs
[Top] [All Lists]

Re: xfs metadata overhead

To: Danny Shavit <danny@xxxxxxxxxxxxxxxxx>
Subject: Re: xfs metadata overhead
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sat, 25 Jun 2016 08:51:45 +1000
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAC=x_0g_iktOKOKiRF5Ku7N-PSbCXOR+Amhm577YjNYQaRPjeA@xxxxxxxxxxxxxx>
References: <CAC=x_0jDYb17Vh97Led7XXDiUMcUTJbpJ2Dw45gn=D0_w0K5VQ@xxxxxxxxxxxxxx> <20160622225117.GX12670@dastard> <CAC=x_0hdvm7SSP8EOAdUwLa-k3a3p7p7CRj8tyCnEx=As7A6jw@xxxxxxxxxxxxxx> <71fbc905-ef05-126a-5c7f-c68c9018763c@xxxxxxxxxxx> <CAC=x_0hnGQHAenv985+FusWxK_63AatB_XK_mqbAmyt=OxqYrg@xxxxxxxxxxxxxx> <b920a8ec-6410-1daa-809c-04b48db24c0a@xxxxxxxxxxx> <CAC=x_0g_iktOKOKiRF5Ku7N-PSbCXOR+Amhm577YjNYQaRPjeA@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>