[Lustre-devel] F/S stats visualisation

Johann Lombardi johann at whamcloud.com
Tue May 17 05:47:57 PDT 2011

On Tue, May 17, 2011 at 02:13:37PM +0200, rf at q-leap.de wrote:
> Which #blocks? The one of the MDT or the one of the whole FS?

The #blocks on the MDT.

> Does that imply I'm doing something wrong?

Lustre is just *very* conservative. If you format your MDT with a #blocks/#inodes ratio of 1, you won't get this problem.

> What is an EA block anyway?

The file striping configuration is stored in an extended attribute. Depending on the number of file stripes (can be changed dynamically with lfs setstripe), this extended attribute is stored either in the inode core or in an additional data block. In the latter, you need to alloate one data block for each file creation.

> We haven't activated any striping.

Then you use the default stripe count which is 1 and the extended attribute fits in the inode.
As i said in my first email, we could probably do better and handle this at mkfs time. Andreas' patch (http://review.whamcloud.com/#change,480) introducing --stripe-count-hint should help in this regard.


More information about the lustre-devel mailing list