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-2350 Lustre <p>Here is console log from client:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>===== Check Lustre quotas usage/limits ====================================== quotacheck failed: Operation not supported Listing quotas for user "quota_usr" and group "quota_usr" on client-5,client-6... client-5: Disk quotas for user quota_usr (uid 60000): client-5: Unexpected quotactl error: Operation not supported client-5: Filesystem kbytes quota limit grace files quota limit grace client-5: /mnt/lustre [0] [0] [0] - [0] [0] [0] - client-5: Some errors happened when getting quota info. Some devices may be not working or deactivated. The data in "[]" is inaccurate. </pre> </div></div> <p>dmesg from client-5</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: DEBUG MARKER: ===== Check Lustre quotas usage/limits ====================================== Lustre: DEBUG MARKER: cancel_lru_locks mdc start Lustre: DEBUG MARKER: cancel_lru_locks osc start LustreError: 4995:0:(osc_quota.c:277:osc_quotactl()) ptlrpc_queue_wait failed, rc: -95 LustreError: 4995:0:(mdc_request.c:1431:mdc_quotactl()) ptlrpc_queue_wait failed, rc: -95 LustreError: 4995:0:(lmv_obd.c:3125:lmv_quotactl()) getquota on mdt 0 failed. -95 LustreError: 4995:0:(mdc_request.c:1431:mdc_quotactl()) ptlrpc_queue_wait failed, rc: -95 LustreError: 4995:0:(osc_quota.c:277:osc_quotactl()) ptlrpc_queue_wait failed, rc: -95 </pre> </div></div> Before upgrade:<br/> server 1.8.8-wc1 RHEL5<br/> client 1.8.8-wc1 RHEL5/RHEL6<br/> <br/> After upgrade:<br/> server lustre-master build #1043 RHEL6<br/> client luster-master build #1043 RHEL6 LU-2350

Unexpected quotactl error after upgrade from 1.8.8-wc1 to master: Operation not supported

Bug Minor Closed Won't Fix Niu Yawei Sarah Liu sdsc Sat, 17 Nov 2012 02:00:03 +0000 Mon, 17 Jul 2017 14:20:31 +0000 Mon, 17 Jul 2017 14:20:31 +0000 Lustre 2.4.0 0 6 <p>Sarah, quotacheck isn't supported any more in 2.4. Instead, tunefs.lustre --quota should be run against the targets formatted with 1.8. Also the 1.8 clients won't be fully interoperable with 2.4 servers as far as quota is concerned. Customers will have to migrate to 1.8.9.</p> <p>upgraded Lustre server from 1.8.7 to 2.4.2. <br/> Did what was recommented, "tunefs.lustre --quota &lt;devices&gt;".</p> <p> lctl get_param osd-<b>.</b>.quota_slave.info</p> <p>osd-ldiskfs.puma-OST000e.quota_slave.info=<br/> target name: puma-OST000e<br/> pool ID: 0<br/> type: dt<br/> quota enabled: none<br/> conn to master: not setup yet<br/> space acct: ug<br/> user uptodate: glb<span class="error">&#91;0&#93;</span>,slv<span class="error">&#91;0&#93;</span>,reint<span class="error">&#91;1&#93;</span><br/> group uptodate: glb<span class="error">&#91;0&#93;</span>,slv<span class="error">&#91;0&#93;</span>,reint<span class="error">&#91;1&#93;</span></p> <p>showed OSTs quota noenable. Then ran:</p> <p> lctl conf_param meerkat.quota.ost=ug</p> <p><span class="error">&#91;root@puma-oss-13-2 ~&#93;</span># lctl get_param osd-<b>.</b>.quota_slave.info<br/> osd-ldiskfs.puma-OST0006.quota_slave.info=<br/> target name: puma-OST0006<br/> pool ID: 0<br/> type: dt<br/> quota enabled: ug<br/> conn to master: not setup yet<br/> space acct: ug<br/> user uptodate: glb<span class="error">&#91;0&#93;</span>,slv<span class="error">&#91;0&#93;</span>,reint<span class="error">&#91;1&#93;</span><br/> group uptodate: glb<span class="error">&#91;0&#93;</span>,slv<span class="error">&#91;0&#93;</span>,reint<span class="error">&#91;1&#93;</span></p> <p>But on client side, I don't see usages prior to upgrading anymore.</p> <p>Haisong</p> <p>Niu</p> <p>Could you please advise on this one?</p> <p>Thanks</p> <p>Peter</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lctl conf_param meerkat.quota.ost=ug [root@puma-oss-13-2 ~]# lctl get_param osd-..quota_slave.info osd-ldiskfs.puma-OST0006.quota_slave.info= target name: puma-OST0006 pool ID: 0 type: dt quota enabled: ug conn to master: not setup yet space acct: ug user uptodate: glb[0],slv[0],reint[1] group uptodate: glb[0],slv[0],reint[1] </pre> </div></div> <p>quota slave on OST didn't connect to master yet, did you upgrade MDT and enable quota on MDT by tunefs as well?</p> <blockquote></blockquote> <p>But on client side, I don't see usages prior to upgrading anymore.</p> {qutoe} <p>as Johann mentioned, you need to upgrade client to 1.8.9 or later to interoperate with the new quota in 2.4.</p> <p>BTW, you need to upgrade the e2fsprogs to 1.42.7-wc2 or later (which has a important fix for quota).</p> <p>Hi Yawei,</p> <p>MDT was enabled with quota as well, even though I though it was optional because it was only for the inode quota and we didn't want to enable inode quota.</p> <p>2 questions:</p> <p>1) what does it mean "OST didn't connect to master yet"? How to connect to master?</p> <p>2) Does upgrading e2fsprogs require offline the file-system?</p> <p>thanks,<br/> Haisong</p> <p>As far as question 2), need not offline filesystems to upgrade e2fsprogs. It is merely a set of user space tools and utilities. Nothing in it runs continuously while lustre is running.</p> <blockquote> <p>1) what does it mean "OST didn't connect to master yet"? How to connect to master?</p></blockquote> <p>The quota_slave.info shows "conn to master: not setup yet", which means slave(ost) didn't connect to master(mdt) yet, and quota can't be enforced. Slave will connect to master automatically.</p> <p>Close old 1.8 issue.</p> Related LU-4761 Development Rank 1|hzvcgn: Rank (Obsolete) 5604 Severity