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-13603 Lustre <p> On the client that discovered wrong nids we get.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> lnetctl peer show ...... - primary nid: 10.151.27.65@o2ib Multi-Rail: True peer ni: - nid: 10.151.27.65@o2ib state: NA - nid: 10.151.27.62@o2ib state: NA </pre> </div></div> <p>On the server with 10.151.27.65</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> nbp8-oss4 ~ # lctl list_nids 10.151.27.65@o2ib </pre> </div></div> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> nbp8-oss1 ~ # lctl list_nids 10.151.27.62@o2ib </pre> </div></div> LU-13603

Multirail discovers wrong nids (randomly)

Bug Critical Resolved Incomplete Amir Shehata Mahmoud Hanafi Wed, 27 May 2020 01:50:39 +0000 Wed, 6 Jan 2021 12:52:57 +0000 Wed, 6 Jan 2021 12:52:57 +0000 0 6 <p>Amir</p> <p>Could you please advise?</p> <p>Thanks</p> <p>Peter</p> <p>Is there a particular sequence of operations which causes this to happen?</p> <p>There were a few problems fixed around discovery. They stem from toggling discovery on/off. Also in some cases the PUSH step of discovery is not done, which could cause similar symptoms. IE the two peers endup with different views. </p> <p>Below is a list of patches landed recently which fix these issues.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> LU-13477 lnet: Force full discovery cycle LU-13478 lnet: handle discovery off properly LU-13471 lnet: use the same src nid <span class="code-keyword">for</span> discovery LU-12312 lnet: handle no discovery flag LU-13028 lnet: advertise discovery when toggled LU-13278 lnet: Reconcile discovery push and reply handling </pre> </div></div> <p>We were doing software updates. But during the update we experienced hardware issue and the servers were down for several hours. </p> <p>This can be closed</p> Related Development Rank 1|i0119z: Rank (Obsolete) 9223372036854775807 Severity