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-6071 Lustre <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> kernel:LustreError: 3652:0:(mdt_handler.c:2706:mdt_object_lock0()) ASSERTION( !(ibits &amp; (MDS_INODELOCK_UPDATE | MDS_INODELOCK_PERM)) ) failed: lustre-MDT0001: wrong bit 0x2 <span class="code-keyword">for</span> remote obj [0x200000007:0x1:0x0] kernel:LustreError: 3652:0:(mdt_handler.c:2706:mdt_object_lock0()) LBUG </pre> </div></div> <p>To reproduce the issue two-node cluster is enough.</p> <p>On server:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">#MDSCOUNT=3 lustre/tests/llmount.sh #lctl set_param mdt.*.enable_remote_dir=1 #lctl set_param mdt.*.enable_remote_dir_gid=1122 </pre> </div></div> <p>Client</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">#mount -t lustre 172.16.157.136@tcp0:/lustre /mnt/lustre #lustre/utils/lfs mkdir -i 1 /mnt/lustre/mdt1 </pre> </div></div> <p>Server is failed with LBUG above.</p> Patchless client from branch b2_6 <br/> 07-19-2014 Intel Corporation<br/> * version 2.6.0<br/> <br/> Server from b2_5 (e835226b17309ec21fd7b46cf397e5fd557049bd)<br/> 09-03-2014 Intel Corporation<br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;* version 2.5.3 LU-6071

LBUG during mkdir -i 1 from 2.6.0 client to 2.5.3 server

Bug Critical Resolved Fixed Di Wang Artem Blagodarenko HB mq115 patch Fri, 26 Dec 2014 09:22:23 +0000 Wed, 4 Dec 2019 03:01:19 +0000 Thu, 22 Jan 2015 20:06:52 +0000 Lustre 2.6.0 Lustre 2.5.3 Lustre 2.7.0 0 7 <p>Artem Blagodarenko (artem_blagodarenko@xyratex.com) uploaded a new patch: <a href="http://review.whamcloud.com/13189" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13189</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6071" title="LBUG during mkdir -i 1 from 2.6.0 client to 2.5.3 server" class="issue-link" data-issue-key="LU-6071"><del>LU-6071</del></a> client: Fix mkdir -i 1 from DNE2 client to DNE1 server<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 590ee871adccda9ac52d02d888b2c27916be22cb</p> <p>Artem Blagodarenko (artem_blagodarenko@xyratex.com) uploaded a new patch: <a href="http://review.whamcloud.com/13190" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13190</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6071" title="LBUG during mkdir -i 1 from 2.6.0 client to 2.5.3 server" class="issue-link" data-issue-key="LU-6071"><del>LU-6071</del></a> client: Fix mkdir -i 1 from DNE2 client to DNE1 server<br/> Project: fs/lustre-release<br/> Branch: b2_6<br/> Current Patch Set: 1<br/> Commit: cc680fa5575c8ccc110e8293d1e5bff3cd92007d</p> <p>Artem, thanks for the patch. We're not planning to land any patches for b2_6, since that is not a maintenance branch. Is this patch needed for b2_5 or master? Is the MDS LASSERT() removed on master or can it still be triggered by a bad client? Could you please also submit a patch for b2_5 to make the LASSERT() just return an error in this case (-EREMOTE? or even better pass the RPC on to the proper MDT). </p> <blockquote> <p>Artem, thanks for the patch. We're not planning to land any patches for b2_6, since that is not a maintenance branch. Is this patch needed for b2_5 or master? </p></blockquote> <p>Andreas, all clients &gt;= b2_6 should be patched. So, I believe I need to rebase this patch to master branch and upload again. Should I?</p> <blockquote> <p> Is the MDS LASSERT() removed on master or can it still be triggered by a bad client? </p></blockquote> <p>MDS LASSERT is removed on master. MDS from master can fine accept old and new clients.</p> <blockquote> <p>Could you please also submit a patch for b2_5 to make the LASSERT() just return an error in this case (-EREMOTE? or even better pass the RPC on to the proper MDT).</p></blockquote> <p>So, we need another one patch for b2_5 server? Not a problem I will make it. I believe adding -EREMOTE message is better. Quite the same error returns server from master then it gets request to wrong MDT (see CLIENT-MDT compatibility chapter in <a href="http://wiki.opensfs.org/images/f/ff/DNE_StripedDirectories_HighLevelDesign.pdf" class="external-link" target="_blank" rel="nofollow noopener">http://wiki.opensfs.org/images/f/ff/DNE_StripedDirectories_HighLevelDesign.pdf</a>).</p> <blockquote> <p>In DNE Phase II rename request will be sent to the MDT where the target file is located. This is different from DNE Phase I. An old client (&lt;= Lustre software version 2.4.0) will still send the request to the MDT where the source parent is, and the source parent will return -EREMOTE to the old client. A 2.4.0 client does not understand -EREMOTE so a patch will be added to 2.4 series to redirect rename request to the MDT where the target file is, if it gets -EREMOTE from the MDT.</p></blockquote> <p>Artem Blagodarenko (artem_blagodarenko@xyratex.com) uploaded a new patch: <a href="http://review.whamcloud.com/13361" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13361</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6071" title="LBUG during mkdir -i 1 from 2.6.0 client to 2.5.3 server" class="issue-link" data-issue-key="LU-6071"><del>LU-6071</del></a> mdt: Fix mkdir -i 1 from DNE2 client to DNE1 server<br/> Project: fs/lustre-release<br/> Branch: b2_5<br/> Current Patch Set: 1<br/> Commit: 7b8cffa906b6ae0de5c16a92b315ea973cdd920a</p> <p>I uploaded patch for 2.5 server. Now 2.6 client returns if try lfs mkdir -i 1 to 2.5 server</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"># lustre/utils/lfs mkdir -i 1 /mnt/lustre/mdt1 error on LL_IOC_LMV_SETSTRIPE <span class="code-quote">'/mnt/lustre/mdt1'</span> (3): <span class="code-object">Object</span> is remote error: mkdir: create stripe dir <span class="code-quote">'/mnt/lustre/mdt1'</span> failed </pre> </div></div> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/13189/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13189/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6071" title="LBUG during mkdir -i 1 from 2.6.0 client to 2.5.3 server" class="issue-link" data-issue-key="LU-6071"><del>LU-6071</del></a> client: Fix mkdir -i 1 from DNE2 client to DNE1 server<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 426f9c0365d1e8528b07b89f1d7c0a7f2f80e3a5</p> <p>Landed for 2.7</p> <p>There is also server-side patch patch: <a href="http://review.whamcloud.com/13361" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13361</a> for 2_5 branch that need to be inspected (only one +1)</p> <p>Artem Blagodarenko (artem_blagodarenko@xyratex.com) uploaded a new patch: <a href="http://review.whamcloud.com/14401" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14401</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6071" title="LBUG during mkdir -i 1 from 2.6.0 client to 2.5.3 server" class="issue-link" data-issue-key="LU-6071"><del>LU-6071</del></a> client: Fix mkdir -i 1 from DNE2 client to DNE1 server<br/> Project: fs/lustre-release<br/> Branch: b2_5<br/> Current Patch Set: 1<br/> Commit: 8c6cd3b49a5cceb4045825651a6a0543ab893b4a</p> <p> <a href="http://review.whamcloud.com/14401" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14401</a> is abandoned, but <a href="http://review.whamcloud.com/13361" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13361</a> inspection is still in progress.</p> <p>&gt;<a href="http://review.whamcloud.com/14401" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14401</a> is abandoned, but <a href="http://review.whamcloud.com/13361" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13361</a> inspection is still in progress.<br/> I see this issue is closed. Sorry, are we going to land this sever patch to b2_5? Thanks.</p> Duplicate Related Development Rank 1|hzx327: Rank (Obsolete) 16896 Severity