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-5830 Lustre <p>When trying to enable and use lnet start/stop script to shutdown a stand-alone Lustre Server it fails with errors during modules unload. This comes from a wrong list/order of modules to be unloaded. It would be safer to use lustre_rmmod to do so instead.<br/> Master patch is at <a href="http://review.whamcloud.com/12513" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12513</a>.</p> LU-5830

use lustre_rmmod in lnet start/stop script

Bug Minor Resolved Fixed Bruno Faccini Bruno Faccini Fri, 31 Oct 2014 08:43:13 +0000 Sat, 6 May 2017 01:00:20 +0000 Mon, 17 Nov 2014 16:02:26 +0000 Lustre 2.7.0 Lustre 2.5.4 Lustre 2.7.0 Lustre 2.5.4 0 8 <p>Here is the back-ported patch for Lustre b2_5 branch: <a href="http://review.whamcloud.com/12587" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12587</a></p> <p>Landed for 2.7</p> <p>Bruno, I noticed that this patch was very similar to <a href="http://review.whamcloud.com/5478" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5478</a> "<a href="https://jira.whamcloud.com/browse/LU-2669" title="Init script &quot;lnet stop&quot; fails due to incorrect module list" class="issue-link" data-issue-key="LU-2669"><del>LU-2669</del></a> scripts: Change behavior of lustre_rmmod" but doesn't do quite the same thing. That patch removed the Lustre modules before stopping LNet, then removed the ptlrpc/lnet/libcfs modules afterward.</p> <p>Is there still value in the changes to <tt>lustre_rmmod</tt> that <a href="http://review.whamcloud.com/5478" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5478</a> made, or should it be abandoned?</p> <p>Andreas, you are right they are very similar, and particularly both tickets reason since they both bring out the same flaw in lnet shutdown script. The main difference comes from the need to strictly follow the 3 steps procedure that you have described, which I have never found to be necessary, but may be I am wrong?<br/> Also last patch-set of change #5478 for <a href="https://jira.whamcloud.com/browse/LU-2669" title="Init script &quot;lnet stop&quot; fails due to incorrect module list" class="issue-link" data-issue-key="LU-2669"><del>LU-2669</del></a> has triggered a lot of tests failures that may be caused by the changes it applies to lustre_rmmod, when my patch has not encountered failures during auto-tests.</p> <p>Bruno, have you ever done testing with LNet routing to see if that could cause problems that aren't seen in our regular testing? I can't imagine that this three-step shutdown process was created unless there was a reason to do so.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/12587/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12587/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-5830" title="use lustre_rmmod in lnet start/stop script" class="issue-link" data-issue-key="LU-5830"><del>LU-5830</del></a> scripts: use lustre_rmmod in lnet start/stop script<br/> Project: fs/lustre-release<br/> Branch: b2_5<br/> Current Patch Set: <br/> Commit: e5966bdbb7c7644cc04580ad6b4a9006def3f758</p> Blocker Duplicate LU-2669 Related Development Rank 1|hzwzvr: Rank (Obsolete) 16352 Severity