>> There is also a feature to allow specifying "-p u:username" to lookup up the >> numeric UID for use as the PROJID to simplify using the common "PROJID == >> UID" workflow.
Project involves group of people. We use same numeric ID for UNIX group and project. It can be nice to add option "-p g:groupname" if that does not make a trouble. Best regards, Alex. From: lustre-discuss <lustre-discuss-boun...@lists.lustre.org> on behalf of Andreas Dilger via lustre-discuss <lustre-discuss@lists.lustre.org> Date: Thursday, March 27, 2025 at 13:48 To: Einar Næss Jensen <einar.nass.jen...@ntnu.no> Cc: lustre-discuss@lists.lustre.org <lustre-discuss@lists.lustre.org> Subject: Re: [lustre-discuss] question regarding lustre project quotas vs user and/or group quota This is my recommendation as well. If you want the user and project quotas to be disjoint, then use projid = UID for the home directories, and e. g. projid = UID + 1M for the "project" directories. Then they can be assigned different ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd This is my recommendation as well. If you want the user and project quotas to be disjoint, then use projid = UID for the home directories, and e.g. projid = UID + 1M for the "project" directories. Then they can be assigned different quotas for the different parts of the filesystem. Otherwise, if there are user, group, and project quotas all enabled at the same time, then the inode/space usage limit will be applied by the lowest limit that is hit. In some cases this is desirable (e.g. a project quota of 1TB shared among a group of 10 users each with 20TB limit). In other cases this can be confusing and it is better to just use the projid quotas for different parts of the filesystem. There is patch https://review.whamcloud.com/46144<https://urldefense.us/v3/__https:/review.whamcloud.com/46144__;!!G_uCfscf7eWS!bFB8KNEdVL9XS9Guu7Vwa-KrPwRCIkZTpafT5-_O_EwFyivbwYnc_QREZ9u_8Cad3TLRI1JbgdNUIdJnJpjcXfK2Wv_IXA$> ("LU-13335 utils: allow projid lookup by name") that will simplify using projids by allowing lookup by name instead of only by number. There is also a feature to allow specifying "-p u:username" to lookup up the numeric UID for use as the PROJID to simplify using the common "PROJID == UID" workflow. This patch isn't landed yet, but will become available in a release once the development is finished. Cheers, Andreas On Mar 26, 2025, at 09:18, Einar Næss Jensen via lustre-discuss <lustre-discuss@lists.lustre.org> wrote: Hello Åke. Thank you for confirming our suspicion. We have come to the same conclusion on our larger systems (DDN & Clusterstor) but we were hoping perhaps in newer lustre versions this was different. Best Regards Einar Næss Jensen ________________________________________ From: Åke Sandgren <ake.sandg...@umu.se> Sent: Wednesday, March 26, 2025 14:57 To: lustre-discuss@lists.lustre.org; Einar Næss Jensen Subject: Re: question regarding lustre project quotas vs user and/or group quota User quota, if enabled, will be affected regardless of where in the file system the file is. We decided to use only project quota, even for users home directory, i.e. $HOME get projectquota for projid = userid and project storage has projid = the project storage gid. Made our life easier ________________________________________ From: lustre-discuss <lustre-discuss-boun...@lists.lustre.org> on behalf of Einar Næss Jensen via lustre-discuss <lustre-discuss@lists.lustre.org> Sent: Wednesday, March 26, 2025 13:50 To: lustre-discuss@lists.lustre.org Subject: [lustre-discuss] question regarding lustre project quotas vs user and/or group quota Hello all I have a question regarding project quotas If we have activated user and project quotas on a file system: Will user quota be affected by what is inside a project/directory quota? How can we prevent user quota being affected by what a user put into a directory/project quota This is on lustre 2.15.x Best Regards Eianr Næss Jensen _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org<https://urldefense.us/v3/__http:/lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org__;!!G_uCfscf7eWS!bFB8KNEdVL9XS9Guu7Vwa-KrPwRCIkZTpafT5-_O_EwFyivbwYnc_QREZ9u_8Cad3TLRI1JbgdNUIdJnJpjcXfIHjoTcAw$> _______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org<https://urldefense.us/v3/__http:/lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org__;!!G_uCfscf7eWS!bFB8KNEdVL9XS9Guu7Vwa-KrPwRCIkZTpafT5-_O_EwFyivbwYnc_QREZ9u_8Cad3TLRI1JbgdNUIdJnJpjcXfIHjoTcAw$> Cheers, Andreas — Andreas Dilger Lustre Principal Architect Whamcloud/DDN
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
