[Lustre-devel] F/S stats visualisation

Johann Lombardi johann at whamcloud.com
Mon May 2 09:32:59 PDT 2011

On Mon, May 02, 2011 at 05:51:36PM +0200, rf at q-leap.de wrote:
> It seems lfs df -i is indeed buggy showing totally bogus numbers
> (see https://bugzilla.lustre.org/show_bug.cgi?id=24489)

In this case, you run df on the server directly, so you are comparing statfs information as returned by ext4/ldiskfs with what you get through lustre (i.e. lfs df or df on a lustre client).
Lustre takes for granted that 1 EA block is needed for each inode (conservative approach) and adjusts the total number of inodes accordingly (see fsfilt_ext3_statfs()).
That being said, with large inode support and mkfs.lustre adapting the inode size based on the default stripe count, i am not sure this "adjustment" makes sense any more. We could instead print a warning at mkfs time when the default stripe count cannot fit in the inode core and #inodes > #blocks.


Johann Lombardi
Whamcloud, Inc.

More information about the lustre-devel mailing list