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-12021 Lustre <p>A lot of messages of "Unknown attr bits: 0x60000" are printed. And they are very annoying.</p> LU-12021

Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server

Bug Minor Resolved Fixed Qian Yingjin Li Xi Tue, 26 Feb 2019 15:43:38 +0000 Wed, 27 Nov 2019 15:25:42 +0000 Thu, 18 Apr 2019 22:35:51 +0000 Lustre 2.11.0 Lustre 2.12.0 Lustre 2.13.0 Lustre 2.12.1 0 6 <p>I believe this isn't a client/server interop issue.  I looked at this at Cray with 2.11 client &amp; server.  I don't have the detailed notes, but I concluded the issue was the kernel/VFS was presenting a new attr bit (ie Linux has added a new attr bit), and the MDS was complaining about it because it didn't recognize it.  We decided it was harmless and low priority to fix.  We initially saw this only on SLES, but I've seen it on CentOS recently.</p> <p>Patrick, I think this is caused by Lazy Size on MDT feature which is just introduced in 2.12. So, not a surprise that 2.11 client doesn't have the problem.</p> <p>No, 2.11 <b>did</b> have the problem, <a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=lixi_wc" class="user-hover" rel="lixi_wc">lixi_wc</a>.  I specifically looked at it and identified the bit as a new attr bit added in newer kernels.  I would give more detail but I don't have my notes, since they're internal at Cray.</p> <p>Ah, are you still able to get the exact error message?</p> <p>For the flags of 0x60000, I think it is caused by LSoM because these two flags are LSoM flags:</p> <p>#define MDS_ATTR_LSIZE 0x20000ULL /* = 131072 */<br/> #define MDS_ATTR_LBLOCKS 0x40000ULL /* = 262144 */</p> <p>I confirmed with the customer that they are using clients of 2.12 with Ubuntu.</p> <p>I guess the 2.11 problem has a different flag value printed in mdt_attr_valid_xlate()? And then it should be caused by some kernel update of the bits.</p> <p>I am not, and I just did the same looking as you...  I agree, it must've been a different bit, or maybe I'm crazy and we <b>were</b> testing 2.12.  I don't think so, but...  Certainly, those are the LSOM bits.</p> <p>And there are no new attr bits even in the current Linus kernel...</p> <p>Hm.  I will see if I can dig up the error from someone at Cray. Odd.  For now, ignore me. <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>It would be good to implement one or more of the mechanisms proposed in <a href="https://jira.whamcloud.com/browse/LU-11928" title="Noisy &quot;mdt_attr_valid_xlate()) Unknown attr bits: 0x60000&quot;" class="issue-link" data-issue-key="LU-11928"><del>LU-11928</del></a>. Probably the best would be a new <tt>OBD_CONNECT_LSOM</tt> flag send from the client and checked by the server, so that the client doesn't send these flags to old servers that don't support them.</p> <p>Yingjin Qian (qian@ddn.com) uploaded a new patch: <a href="https://review.whamcloud.com/34343" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/34343</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-12021" title="Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server" class="issue-link" data-issue-key="LU-12021"><del>LU-12021</del></a> lsom: Add an OBD_CONNECT2_LSOM connect flag<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 11e2b730944d3afbe62f6559a316929e58927a20</p> <p>Aurelien Degremont (degremoa@amazon.com) uploaded a new patch: <a href="https://review.whamcloud.com/34412" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/34412</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-12021" title="Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server" class="issue-link" data-issue-key="LU-12021"><del>LU-12021</del></a> mdt: make useless error message a debug one<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: acf12670e6f9acd1fac9a999a3f37ccc5c5d3c6b</p> <p>Minh Diep (mdiep@whamcloud.com) uploaded a new patch: <a href="https://review.whamcloud.com/34663" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/34663</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-12021" title="Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server" class="issue-link" data-issue-key="LU-12021"><del>LU-12021</del></a> lsom: Add an OBD_CONNECT2_LSOM connect flag<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: 1<br/> Commit: a0e2915c67fed503cdadca3af23430095b7000c0</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/34343/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/34343/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-12021" title="Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server" class="issue-link" data-issue-key="LU-12021"><del>LU-12021</del></a> lsom: Add an OBD_CONNECT2_LSOM connect flag<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: fdd2c5d3a6e5f866e5ca887064e9ed37316af234</p> <p>Landed for 2.13</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/34663/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/34663/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-12021" title="Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server" class="issue-link" data-issue-key="LU-12021"><del>LU-12021</del></a> lsom: Add an OBD_CONNECT2_LSOM connect flag<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: <br/> Commit: 03caa311ca920eb94cdb73935c46364e0ebe13a9</p> Duplicate LU-11928 Development Rank 1|i00cbr: Rank (Obsolete) 9223372036854775807 Severity