Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Lustre 2.17.0
-
3
-
9223372036854775807
Description
It is common practice to use project quotas instead of user quotas in a Lustre filesystem to allow having different quotas for different parts of the filesystem and to allow the project quota accounting quickly determine space usage for users in different subdirectory trees (e.g. "/lustre/home/adilger", "/lustre/project/adilger", "/lustre/scratch/adilger"). In such configurations, it is common that the "/lustre/home" subtree map projid == userid to simplify ID management, while "/lustre/scratch/adilger" might be UID+100000 and "/lustre/project/adilger" might be UID+200000.
It should be possible to configure "lfs quota --projid PROJNAME", "lfs project --projid PROJNAME", and "lfs find --projid PROJNAME" and related commands to fall back to looking up the numeric UID for PROJNAME when a project name is not found in /etc/projid. This reduces configuration overhead for the project IDs, and would allow using a network database (e.g. LDAP or sssd in /etc/resolv.conf) for doing the "projid" lookups using the username. This should be configurable with a directive in /etc/projid.
Options that have been discussed:
- store some directive as a comment in the file, like "# config: projname=passwd" or "# config: projname=group" that would redirect all future projname or projid lookups to use getpwnam()/getpwuid() or getgrnam()/getgrgid() as appropriate to look up the supplied name/ID. This has the advantage that it maintains compatibility with XFS, but means that all of the comment lines need to be parsed.
- store some directive as a "special" entry, like "*:passwd:use passwd entry for projid mapping" or "*:group:use group entry for projid mapping" (comments are optional and for reference only).
Attachments
Issue Links
- is related to
-
-
- Open
-