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.

This sets a much smaller granularity. It is specified to request a new quota in units of<br />

100 MB and 500 inodes, respectively. If we look at the example again:<br />

# lfs quota -u bob /mnt/lustre<br />

Disk quotas for user bob (uid 500):<br />

Filesystem blocks quota limit grace files quota limit grace<br />

/mnt/lustre 207432 307200 30920 1041 10000 11000<br />

lustre-MDT0000_UUID 992 0 102400 1041 05000<br />

lustre-OST0000_UUID 103204* 0 102400<br />

lustre-OST0001_UUID 103236* 0 102400<br />

The total quota of 30,920 is alloted to user bob, which is further disributed to two<br />

OSTs and one MDS with a 102,400 block quota.<br />

Note – Values appended with “*” show the limit that has been over-used (exceeding<br />

the quota), and receives this message Disk quota exceeded. For example:<br />

\<br />

$ cp: writing `/mnt/lustre/var/cache/fontconfig/<br />

beeeeb3dfe132a8a0633a017c99ce0-x86.cache’: Disk quota exceeded.<br />

The requested quota of 300 MB is divided across the OSTs. Each OST has an initial<br />

allocation of 100 MB blocks, with iunit limiting to 5000.<br />

Note – It is very important to note that the block quota is consumed per OST and<br />

the MDS per block and inode (there is only one MDS for inodes). Therefore, when<br />

the quota is consumed on one OST, the client may not be able to create files<br />

regardless of the quota available on other OSTs.<br />

Chapter 9 Configuring Quotas 9-7

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

Saved successfully!

Ooh no, something went wrong!