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-150 Lustre <p>We can't see correct quota output after the recovery. Once run quotacheck again, the 'lfs quota' shows right output. Here is quick reproducer. We confirmed same situation happens on both lustre-1.8.4 and lustre-1.8.5.</p> <p>0. Normal case<br/> It's no problem.</p> <p><span class="error">&#91;test@r03 test&#93;</span>$ lfs quota -u test /mnt/lustre<br/> Disk quotas for user test (uid 501):<br/> Filesystem kbytes quota limit grace files quota limit grace<br/> /mnt/lustre 4 0 0 - 1 0 0 -</p> <p>1. 'lfs quota' on during the recovery<br/> Umount/mount an OST and occurs the recovery. The during the recovery, when we run 'lfs quota' command, the some data are inaccurate.</p> <p>Disk quotas for user test (uid 501):<br/> Filesystem kbytes quota limit grace files quota limit grace<br/> /mnt/lustre <span class="error">&#91;0&#93;</span> 0 0 - <span class="error">&#91;0&#93;</span> 0 0 -<br/> Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate.</p> <p>2. 'lfs quota' after the recovery</p> <p>Even after finish the recovery, inaccurate output still can't fixed.</p> <p>Disk quotas for user test (uid 501):<br/> Filesystem kbytes quota limit grace files quota limit grace<br/> /mnt/lustre <span class="error">&#91;0&#93;</span> 0 0 - <span class="error">&#91;0&#93;</span> 0 0 -<br/> Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate.</p> <p>3. run quotacheck again</p> <p>the correct output shows up once we run quotacheck again after the recovery.</p> <p>Disk quotas for user test (uid 501):<br/> Filesystem kbytes quota limit grace files quota limit grace<br/> /mnt/lustre 4 0 0 - 1 0 0 -</p> LU-150

inaccurate quota output after the recovery

Bug Blocker Resolved Won't Fix Niu Yawei Shuichi Ihara Mon, 21 Mar 2011 20:47:24 +0000 Tue, 28 Jun 2011 15:01:40 +0000 Mon, 28 Mar 2011 02:01:38 +0000 Lustre 1.8.6 Lustre 1.8.6 0 2 <p>Niu</p> <p>Could you please look into this issue?</p> <p>Thanks</p> <p>Peter</p> <p>Hi, Ihara</p> <p>This is because the quota on the umount/mount OST was not turned on, so lfs reported the usage might be inaccurate. You just need to run 'lfs quotaon' again to turn on quota on all OSTs after that.</p> <p>Thanks</p> <ul class="alternate" type="square"> <li>Niu</li> </ul> <p>Niu, </p> <p>'lfs quotaon' helps to avoid 'lfs quotacheck' again after the recovery, but still need to run 'lfs quotaon' after the every recovery finish. The writing of ost.quota_type=ug to all OSTs, mdt.quota_type=ug to MDT are only a solution to keep the enabling the quota?</p> <p>we think about the failover situation of this.</p> <p>Ihara</p> <p>Hi, Ihara</p> <p>Right, quota should not be automatically enabled after filesystem mounted, unless there are configuration like ost.quota_type, mdt/mdd.quota_type (I think it's the best way to auto turn on quota for lustre), or some auto-scripts to do it (like local fs usually does).</p> <p>Thanks</p> <ul class="alternate" type="square"> <li>Niu</li> </ul> <p>OK, thanks! I also tested again and confirmed this. It was not bug. I was sorry this stupid question. I've passed quota related information to the customer. Please close this ticket.</p> <p>Ihara</p> <p>Thank you, Ihara. Set it as 'Won't fix'.</p> Development Rank 1|hzw09z: Rank (Obsolete) 10124 Severity