From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 86A347CA2 for ; Fri, 24 Jun 2016 17:51:51 -0500 (CDT) Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by relay1.corp.sgi.com (Postfix) with ESMTP id 579E38F8037 for ; Fri, 24 Jun 2016 15:51:51 -0700 (PDT) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by cuda.sgi.com with ESMTP id tPPaDse7teuoWInR for ; Fri, 24 Jun 2016 15:51:48 -0700 (PDT) Date: Sat, 25 Jun 2016 08:51:45 +1000 From: Dave Chinner Subject: Re: xfs metadata overhead Message-ID: <20160624225145.GF12670@dastard> References: <20160622225117.GX12670@dastard> <71fbc905-ef05-126a-5c7f-c68c9018763c@sandeen.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Danny Shavit Cc: Eric Sandeen , xfs-oss 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