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-14114 Lustre <p>A device can be in fatal state, if the cable was disconnected, or the port brought down on the switch side. In these cases, the LND (o2iblnd for now), will flag the device in fatal state. That device will not be used any further. However, it's health will not be decremented. This causes some confusion when examining the state of the node.</p> <p>It is better to print the device status in the output of the <tt>lnetctl net show</tt> command.</p> <p>Basically we need to propagate this value:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> lnet_ni-&gt;ni_fatal_error_on</pre> </div></div> <p>up to user space when we show the net.</p> <p><tt>lustre_lnet_show_net()</tt> and <tt>lnet_get_ni_config()</tt> need to be modified to propagate and print this value.</p> <p>There is space in <tt>lnet_ioctl_config_ni</tt> to add this value without having to add more data structures to the IOCTL API.</p> LU-14114

LNet: print device status in net show command

Bug Minor Resolved Fixed Cyril Bordage Amir Shehata Wed, 4 Nov 2020 21:38:09 +0000 Fri, 30 Jul 2021 17:43:01 +0000 Thu, 22 Jul 2021 03:44:31 +0000 Lustre 2.15.0 0 4 <p>Does it make sense from a usability POV to decrement or immediately set the health down to 0 in this case, so that there is no confusion?</p> <p>Health value was meant to track intermittent errors. Fatal is meant to track the case when the HW tells us that the HCA is not usable. I think it's important to maintain the distinction in the code. I understand though that it might be clearer from a user's perspective. So I don't mind setting that value to 0 when we display it in lnetctl/liblnetconfig user space. But I would rather maintain the distinction in the LNet code. Also it will still be ambiguous if we only display health as 0. Does it mean we've had a series of intermittent failure on that NI and we're currently recovering it? Or does it mean it is in fatal state? If we are in fatal state we don't attempt to recover the NI, because we rely on the HW to tell us when it's up again.</p> <p>Printing out the state of the device in the show output breaks this ambiguity.</p> <p>Cyril Bordage (cbordage@whamcloud.com) uploaded a new patch: <a href="https://review.whamcloud.com/44169" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/44169</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14114" title="LNet: print device status in net show command" class="issue-link" data-issue-key="LU-14114"><del>LU-14114</del></a> lnet: print device status in net show command<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 1807c9fd9ce9d72028c6624ff6a9f0f9c1d1d919</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/44169/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/44169/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-14114" title="LNet: print device status in net show command" class="issue-link" data-issue-key="LU-14114"><del>LU-14114</del></a> lnet: print device status in net show command<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: f75ff33d9fbefd6995a26693032a32a0ba211b51</p> <p>Landed for 2.15</p> Related Development Epic Link LU-13422 Rank 1|i01een: Rank (Obsolete) 9223372036854775807 Severity