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-3220 Lustre <p>Here are the test steps:<br/> 1. setup the system with 2 MDTs and quota enabled.<br/> 2. setup inode quota for user/group quota_usr</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>/usr/bin/lfs setquota -u quota_usr -b 0 -B 10M -i 0 -I 5 /mnt/lustre /usr/bin/lfs setquota -g quota_usr -b 0 -B 10M -i 0 -I 5 /mnt/lustre </pre> </div></div> <p>3. check user quota shows that MDT0 has limit 5 while MD1 has limit 0</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@client-5 tests]# lfs quota -v -u quota_usr /mnt/lustre Disk quotas for user quota_usr (uid 60000): Filesystem kbytes quota limit grace files quota limit grace /mnt/lustre 4 0 10240 - 1 0 5 - lustre-MDT0000_UUID 4 - 0 - 1 - 5 - lustre-MDT0001_UUID 0 - 0 - 0 - 0 - lustre-OST0000_UUID 0 - 0 - - - - - </pre> </div></div> <p>4. create 2 dirs "test" and "test2", "test" is on the default MDT, "test2" is on the second MDT with "lfs mkdir -i 1 ..."<br/> 5. chown to quota_usr for these 2 dirs<br/> 6. I can only touch file under dir "test" while got "Disk quota exceede" in "test2"</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@client-5 tests]# chown quota_usr.quota_usr /mnt/lustre/test [root@client-5 tests]# chown quota_usr.quota_usr /mnt/lustre/test2/ [root@client-5 tests]# lfs quota -v -u quota_usr /mnt/lustre Disk quotas for user quota_usr (uid 60000): Filesystem kbytes quota limit grace files quota limit grace /mnt/lustre 8 0 10240 - 2 0 5 - lustre-MDT0000_UUID 4 - 0 - 1 - 5 - lustre-MDT0001_UUID 4 - 0 - 1* - 1 - lustre-OST0000_UUID 0 - 0 - - - - - [root@client-5 tests]# ./runas -u 60000 -g 60000 touch /mnt/lustre/test2/a1 running as uid/gid/euid/egid 60000/60000/60000/60000, groups: [touch] [/mnt/lustre/test2/a1] touch: cannot touch `/mnt/lustre/test2/a1': Disk quota exceeded [root@client-5 tests]# ./runas -u 60000 -g 60000 touch /mnt/lustre/test/a1 running as uid/gid/euid/egid 60000/60000/60000/60000, groups: [touch] [/mnt/lustre/test/a1] [root@client-5 tests]# </pre> </div></div> LU-3220

Quota doesn't work right with DNE

Bug Major Resolved Fixed Niu Yawei Sarah Liu dne Wed, 24 Apr 2013 18:43:30 +0000 Wed, 16 Oct 2013 00:33:47 +0000 Thu, 11 Jul 2013 05:50:13 +0000 Lustre 2.4.0 Lustre 2.5.0 0 4 <p>Niu, any thoughts?</p> <p>I think this is expected since our minmal iunit size is 1K inodes. The limit in this test is much smaller than 1 iunit size, so they all be ocupied by single MDT (revoke glimpse won't be triggered in this case, because we've reached minimal iunit).</p> <p>As long as we keep using 1K minmal iunit, tests should use inode limit in K unit. (see the quota DNE tests in s-q, test_7e &amp; test_12b)</p> <p>Niu</p> <p>Is there anything that we can do to improve this test while running under DNE? Should we improve our documentation to make is easier to understand what to expect when using DNE in conjunction with quotas?</p> <p>Peter</p> <p>Peter, this is mentioned in Lustre manual:</p> <p>"To reduce quota requests, quota space is initially allocated to QSDs in very large chunks. How much unused quota space can be hold by a target is controlled by the qunit size. When quota space for a given ID is close to exhaustion on the QMT, the qunit size is reduced and QSDs are notified of the new qunit size value via a glimpse callback. Slaves are then responsible for releasing quota space above the new qunit value. The qunit size isn't shrunk indefinitely and there is a minimal value of 1MB for blocks and 1,000 for inodes. This means that the quota space rebalancing process will stop when this mininum value is reached. As a result, quota exceeded can be returned while many slaves still have 1MB or 1,000 inodes of spare quota space."</p> <p>I would advise to add a real-life example with DNE in the manual.<br/> Besides, i wonder whether we should add a warning when someone sets a limit smaller than <span class="error">&#91;bi&#93;</span>unit.</p> <p>Niu, what do you think?</p> <p>The quota commands used for DNE are exactly same as non-DNE, so I don't think the example for DNE is any different from the non-DNE.</p> <p>Ok, I would add a warning message when setting small limit, and maybe we could extend the help descrption of 'lfs setquota' to explain such situation as well.</p> <p><a href="http://review.whamcloud.com/6182" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6182</a></p> <p>I rerun this test with inode limit set to 1005, still hit the same issue.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@client-15 tests]# ./runas -u 60000 -g 60000 touch /mnt/lustre/test2/a1008 running as uid/gid/euid/egid 60000/60000/60000/60000, groups: [touch] [/mnt/lustre/test2/a1008] touch: cannot touch `/mnt/lustre/test2/a1008': Disk quota exceeded [root@client-15 tests]# ./runas -u 60000 -g 60000 touch /mnt/lustre/test2/a1008 running as uid/gid/euid/egid 60000/60000/60000/60000, groups: [touch] [/mnt/lustre/test2/a1008] touch: cannot touch `/mnt/lustre/test2/a1008': Disk quota exceeded [root@client-15 tests]# lfs quota -v -u quota_usr /mnt/lustre Disk quotas for user quota_usr (uid 60000): Filesystem kbytes quota limit grace files quota limit grace /mnt/lustre 52 0 10240 - 2 0 1005 - lustre-MDT0000_UUID 48 - 0 - 1 - 1005 - lustre-MDT0001_UUID 4 - 0 - 1* - 1 - lustre-OST0000_UUID 0 - 0 - - - - - [root@client-15 tests]# ./runas -u 60000 -g 60000 touch /mnt/lustre/test/a1008 running as uid/gid/euid/egid 60000/60000/60000/60000, groups: [touch] [/mnt/lustre/test/a1008] [root@client-15 tests]# </pre> </div></div> <p>Sarah, sorry, the least inode qunit size is 1K but not 1000, I'll update the patch and manual. Thanks.</p> <p>patch landed for 2.5</p> Development Rank 1|hzvowv: Rank (Obsolete) 7862 Severity