https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-7816 Lustre <p> GPFS support default quota setting, but Lustre still dosen't.<br/> Sometimes, for example administrators are not aware of when new<br/> users will be created, and it is common that administrators want to<br/> set a default quota for users/groups when they are created.</p> LU-7816

Add default quota setting support for Lustre

New Feature Minor Resolved Fixed Wang Shilong Wang Shilong patch Thu, 25 Feb 2016 10:50:26 +0000 Thu, 30 Aug 2018 02:46:39 +0000 Tue, 3 Jul 2018 21:08:30 +0000 Lustre 2.12.0 2 14 <p>Wang Shilong (wshilong@ddn.com) uploaded a new patch: <a href="http://review.whamcloud.com/18664" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/18664</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7816" title="Add default quota setting support for Lustre" class="issue-link" data-issue-key="LU-7816"><del>LU-7816</del></a> quota: add default quota setting support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 869bf09b85c092dcb79436293824941cc9760f61</p> <p>Hi Niu,<br/> Can you have a look at this feature patch?</p> <p>Thanks.<br/> Joe</p> <blockquote> <p>I don't quite see how this feature is used, after looking at the patch, my current understanding is: Administrator set default quota for certain user by "lfs setquota --default -u $UID ...", and this setting can be overwritten by real quota setting "lfs setquota -u $UID ...". If there is no real quota setting for certain user, system will turn to use the default one.</p> <p>My question is : If administrator want quota limit on certain user, why don't he just set quota for the user directly? I mean why not just use the "lfs setquota -u $UID ..." to set a 'default' value to the user?</p></blockquote> <p>Ah, my mistake. The default value is per system not per user. </p> <p>I have few questions:</p> <p>1. When default quota is set on system, how can we specify a user/group with no quota limit? No users/groups can have 0 quota limit if there is a non-zero default setting?</p> <p>2. How to set default quota? Set quota to a special UID/GID or introduce a new quota command? (like Q_SET/GET_DEF_USR/GRP) The latter way needs client to support the new qc_cmd, but doesn't need to reserve special UID/GIDs for the default setting. Consequently, the default quota can be stored in the global index (former way) or a separate plain file (latter way).</p> <p>3. How a user/group inherit the default quota setting? For instance, If a user/group has only soft limit, should he inherit the hard limit from default setting? Should the default limit be copied to the entry of other user/group in global index? What if the default value is changed?</p> <p>4. How to notify quota slave when default quota is set/changed/cleared?</p> <p>Probably we'd compose a brief design to address these concerns? Thank you.</p> <p>Silong, are you still working on this? Can we close it? Thanks.</p> <p>Ihara</p> <p>Is this work expected to be a candidate for inclusion in 2.11? </p> <p>Thanks</p> <p>Peter</p> <p>Shilong revised patch and rebased against latest master. We are waiting for review of patches.</p> <p>Hongchao Zhang (hongchao.zhang@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/32306" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32306</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7816" title="Add default quota setting support for Lustre" class="issue-link" data-issue-key="LU-7816"><del>LU-7816</del></a> quota: add default quota setting support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 69ae397cd1b5c88070a3ec05b7d7957e98fa646e</p> <p>Thanks for the patch created by Shilong, and I have some more ideas to implement the default quota based on Shilong's patch.</p> <p>1. the default quota setting is more like a normal setting (it's not related to specific user/group/project account, and it is more like a global setting),<br/> then it's better to be implemented by some global setting, for example, by some special account or some specific quota configuration file.</p> <p>2. To support the default quota based on the existing quota mechanism, we can create a special quota record for the non-enforced quota account,<br/> the special record will have zero hard/soft limit and a flag at the high bits of the grace time (so it can be downgraded to previous Lustre version),<br/> and enforce it with the global default quota setting dynamically.</p> <p>Thanks!</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/32306/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32306/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7816" title="Add default quota setting support for Lustre" class="issue-link" data-issue-key="LU-7816"><del>LU-7816</del></a> quota: add default quota setting support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 530881fe4ee20b56b0426a5c4d3a2b5226768d06</p> <p>Landed for 2.12</p> Blocker LUDOC-405 Related LU-11141 LU-11023 Development End date Wed, 2 Mar 2016 10:50:26 +0000 Rank 1|hzy2on: Rank (Obsolete) 9223372036854775807 Start date Thu, 25 Feb 2016 10:50:26 +0000