23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Additional information:<br />

Grace period — The period of time (in seconds) within which users are allowed to<br />

exceed their soft limit. There are four types of grace periods:<br />

■ user block soft limit<br />

■ user inode soft limit<br />

■ group block soft limit<br />

■ group inode soft limit<br />

The grace periods are applied to all users. The user block soft limit is for all users<br />

who are using a blocks quota.<br />

Soft limit — Once you are beyond the soft limit, the quota module begins to time,<br />

but you still can write block and inode. When you are always beyond the soft limit<br />

and use up your grace time, you get the same result as the hard limit. For inodes and<br />

blocks, it is the same. Usually, the soft limit MUST be less than the hard limit; if not,<br />

the quota module never triggers the timing. If the soft limit is not needed, leave it as<br />

zero (0).<br />

Hard limit — When you are beyond the hard limit, you get -EQUOTA and cannot<br />

write inode/block any more. The hard limit is the absolute limit. When a grace<br />

period is set, you can exceed the soft limit within the grace period if are under the<br />

hard limits.<br />

<strong>Lustre</strong> quota allocation is controlled by two values quota_bunit_sz and<br />

quota_iunit_sz referring to KBs and inodes respectively. These values can be<br />

accessed on the MDS as /proc/fs/lustre/mds/*/quota_* and on the OST as<br />

/proc/fs/lustre/obdfilter/*/quota_*. The /proc values are bounded by<br />

two other variables quota_btune_sz and quota_itune_sz. By default, the<br />

*tune_sz variables are set at 1/2 the *unit_sz variables, and you cannot set<br />

*tune_sz larger than *unit_sz. You must set bunit_sz first if it is increasing by<br />

more than 2x, and btune_sz first if it is decreasing by more than 2x.<br />

Total number of inodes — To determine the total number of inodes, use lfs df -i<br />

(and also /proc/fs/lustre/*/*/filestotal). For more information on using<br />

the lfs df -i command and the command output, see Querying Filesystem Space.<br />

Unfortunately, the statfs interface does not report the free inode count directly, but<br />

instead reports the total inode and used inode counts. The free inode count is<br />

calculated for df from (total inodes - used inodes).<br />

It is not critical to know a filesystem’s total inode count. Instead, you should know<br />

(accurately), the free inode count and the used inode count for a filesystem. <strong>Lustre</strong><br />

manipulates the total inode count in order to accurately report the other two values.<br />

The values set for the MDS must match the values set on the OSTs.<br />

9-8 <strong>Lustre</strong> <strong>1.6</strong> <strong>Operations</strong> <strong>Manual</strong> • September 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!