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-2815 Lustre <p>lfs quota show user over his inode qouta but his not see attached output of lfs quota.</p> LU-2815

quota not correct

Bug Minor Resolved Not a Bug Niu Yawei Mahmoud Hanafi Thu, 14 Feb 2013 14:53:35 +0000 Tue, 29 Oct 2013 18:31:54 +0000 Tue, 29 Oct 2013 18:31:54 +0000 Lustre 2.1.3 0 4 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Disk quotas for user efares (uid 12137): Filesystem kbytes quota limit grace files quota limit grace /nobackupp2 56990092684* 50000000000 75000000000 1w4d18h25m10s 98038* 100000 200000 1w6d23h49m47s </pre> </div></div> <p>Although the inode usage is below the soft limit, the MDT still owns 102400 inodes from the master as shown below:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>nbp2-MDT0000_UUID 287960 - 393216 - 98038 - 102400 - </pre> </div></div> <p>Therefore the quota master started the grace time. The issue is that the quota allocation algorithm only relies on the hard limit and does not take into account the soft limit. The new quota implementation in 2.4 should address this problem.<br/> Meanwhile, you can decrease iunit/itune:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>$ cat /proc/fs/lustre/mds/lustre-MDT0000/quota_iunit_sz 5120 $ cat /proc/fs/lustre/mds/lustre-MDT0000/quota_itune_sz 2560 $ echo 640 &gt; /proc/fs/lustre/mds/lustre-MDT0000/quota_itune_sz $ echo 1280 &gt; /proc/fs/lustre/mds/lustre-MDT0000/quota_iunit_sz </pre> </div></div> <p>Assigning to Niu for any follow-on questions</p> <p>When removing a file, the inode count should drop (provided that the file isn't opened somewhere else) from 113869 to 113868.<br/> As for the quota allocation, the MDS won't release any quota space until inode_usage &lt; quota_owned_by_mds - itune.</p> <p>if the file is open then you shouldn't be able to delete it. The user was able to delete the file. This "inode_usage &lt; quota_owned_by_mds - itune" is used for inode quota or block quota. We are having a lot of reports such issue with quotas.</p> <p>We need a better explanation of how this can occur and why Lustre quota are getting out of sync with real usage.</p> <p>Thanks,<br/> Mahmoud </p> <blockquote> <p>if the file is open then you shouldn't be able to delete it.</p></blockquote> <p>Not at all. You can definitely delete an opened file. The file is unlinked from the namespace (it is actually moved to a special directory called PENDING on the MDT) and then finally deleted once the last opener closes the file. Please see the man page of unlink(2) for more information.</p> <blockquote> <p>This "inode_usage &lt; quota_owned_by_mds - itune" is used for inode quota or block quota.</p></blockquote> <p>I deliberately used the word "inode" above to tell that this logic applies to inode quota management. The same logic is used for blocks on the OST.</p> <blockquote> <p>We are having a lot of reports such issue with quotas.</p></blockquote> <p>Have you decreased iunit and itune as suggested above?</p> <blockquote> <p>We need a better explanation of how this can occur and why Lustre quota are getting out of sync with real usage.</p></blockquote> <p>Could you please try to create a file with this user, run lfs quota -v, delete the file and run lfs quota -v again?</p> <p>Here is another example of quota issue. du and lfs quota don't match</p> <p>nbp6-mds /proc/fs/lustre/lquota/mdd_obd-nbp6-MDT0000 # lfs quota -q -u dposselt /nobackupp6<br/> /nobackupp6 6493023000 7000000000 10000000000 - 164963 200000 500000 -</p> <p>pfe1 /nobackupp6/dposselt # du --apparent-size -sk<br/> 5565676998 .</p> <p>Mahmoud, "du --apparent-size" is usually smaller than actual disk usage, because apparent-size doesn't count the full block size at the end of file, but disk usage does. Quota usage is actual disk usage (maybe not exactly equal to the output of du), could you check the output of "du -sk", I think it should be closer to the output of 'lfs quota'?</p> <p>This can be closed</p> <p>Thanks Mahmoud</p> Development Rank 1|hzvj5z: Rank (Obsolete) 6819 Severity