Lustre Quota Troubleshooting: Difference between revisions
| Line 46: | Line 46: | ||
The values for '''enabled=''' can be '''none''' or any combination of the letters '''u''' (for user), '''g''' (for group) and '''p''' (for project). The default value is '''none''' indicating '''NO QUOTA ENFORCEMENT IS ENABLED''' | The values for '''enabled=''' can be '''none''' or any combination of the letters '''u''' (for user), '''g''' (for group) and '''p''' (for project). The default value is '''none''' indicating '''NO QUOTA ENFORCEMENT IS ENABLED''' | ||
== Quota Modification == | == Accounting and Quota Modification == | ||
If the '''quota''' or '''project''' file system feature is not enabled, stop Lustre, unmount all targets and enable the file system feature(s) with '''tune2fs -O quota, project''' | |||
== References and Links == | == References and Links == | ||
Revision as of 13:37, 30 January 2025
Adding to This Guide
If you have improvements, corrections, or more information to share on this topic please contribute to this page.
Introduction
This document is based on and tested with Lustre 2.15 and LDISKFS. If your Lustre version is older or you are using ZFS, the content may not be applicable.
Space accounting and project ID tracking are enabled by default on a LDISKFS file system. However, quota restrictions for user, group and project are NOT enabled by default. User, Group and Project quota restrictions must be manually enabled on all targets, as well as configuring data/block and/or metadata/inode limits.
Status Verification
SPACE ACCOUNTING
To verify the status of space accounting, run the following on every Lustre node that serves an MDT or OST and has the target mounted.
lctl get_param osd-*.*.quota_slave_*.info
If the value for space acct: is anything other than ugp, likely the quota and/or project file system feature is not enabled. Inspect the superblock information to see if the quota and project features are enabled.
tune2fs -l /dev/sdb | grep features
If quota and project do not appear in the list of Filesystem features:, they will need to be added for space accounting to function
QUOTA
To verify the quota configuration, run the following on every Lustre node that serves an MDT or OST and has the target mounted.
lctl get_param osd-*.*.quota_slave_*.enabled
A MDT will display two different output stanza per target: dt for data/block and md for metadata/inode.
osd-ldiskfs.testfs-MDT0000.quota_slave_dt.enabled=none osd-ldiskfs.testfs-MDT0000.quota_slave_md.enabled=none osd-ldiskfs.testfs-MDT0001.quota_slave_dt.enabled=none osd-ldiskfs.testfs-MDT0001.quota_slave_md.enabled=none
An OST will display only one output stanza per target: dt for data/block.
osd-ldiskfs.testfs-OST0000.quota_slave_dt.enabled=none osd-ldiskfs.testfs-OST0001.quota_slave_dt.enabled=none
The values for enabled= can be none or any combination of the letters u (for user), g (for group) and p (for project). The default value is none indicating NO QUOTA ENFORCEMENT IS ENABLED
Accounting and Quota Modification
If the quota or project file system feature is not enabled, stop Lustre, unmount all targets and enable the file system feature(s) with tune2fs -O quota, project