Lustre 1.6 Operations Manual

9.1.5.2 Quota Limits
Available quota limits depend on the Lustre version you are using.
■
■
■
Lustre version 1.4.11 and earlier (for 1.4.x releases) and Lustre version 1.6.4 and
earlier (for 1.6.x releases) support quota limits less than 4TB.
Lustre versions 1.4.12 and 1.6.5 support quota limits of 4TB and greater in Lustre
configurations with OST storage limits of 4TB and less.
Future Lustre versions are expected to support quota limits of 4TB and greater
with no OST storage limits.
Lustre Version Quota Limit Per User/Per Group OST Storage Limit
1.4.11 and earlier < 4TB n/a
1.4.12 => 4TB 4TB 4TB No storage limit
9.1.5.3 Quota File Formats
Lustre 1.6.5 introduces a new quota file format (v2) for administrative quotas, with
64-bit limits that support large-limits handling. The old quota file format (v1), with
32-bit limits, is also supported. In a future Lustre release, the v2 format will be
added for operational quotas. A few notes regarding the current quota file formats:
■ Lustre 1.6 uses mdt.quota_type to force a specific quota version (2 or 1). 2
■
■
■
■
■
For the v2 quota file format, (OBJECTS/admin_quotafile_v2.{usr,grp})
For the v1 quota file format, (OBJECTS/admin_quotafile.{usr,grp})
If quotas do not exist or look broken, quotacheck creates quota files of a
required name and format.
■ If Lustre is using the v2 quota file format, then quotacheck converts old v1
quota files to new v2 quota files. This conversion is triggered automatically
and is transparent to users. If an old quota file does not exist or looks broken,
then the new v2 quota file will be empty. In case of an error, details can be
found in the kernel log of the MDS.
During conversion of a v1 quota file to a v2 quota file, the v2 quota file is marked
as broken, to avoid its later usage in case of a crash.
Quota module refuses to use broken quota files (keeping quota off).
2. Lustre 1.4 uses a quota file dependent on quota32 configuration options.
Chapter 9 Configuring Quotas 9-11