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-6340 Lustre <p>After running /etc/rc.d/init.d/lnet start, it doesn't configure lnet exactly as defined in /etc/sysconf/lnet.conf. Router is missing, net are not the exact same. </p> <p>This is a minor issue, Amir has suggested 1 line change can fix this problem .</p> <p>the lnet.conf looks like</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@eagle-54vm3 modprobe.d]# more /etc/sysconfig/lnet.conf net: - net: lo nid: 0@lo status: up tunables: peer_timeout: 0 peer_credits: 0 peer_buffer_credits: 0 credits: 0 - net: tcp1 nid: 192.168.201.180@tcp1 status: up interfaces: 0: eth1 tunables: peer_timeout: 181 peer_credits: 8 peer_buffer_credits: 0 credits: 256 route: - net: tcp gateway: 192.168.201.101@tcp1 hop: 1 priority: 0 state: up [root@eagle-54vm3 modprobe.d]# </pre> </div></div> <p>after running lnet start check the system</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@eagle-54vm3 modprobe.d]# lnetctl net show -v net: - net: lo nid: 0@lo status: up tunables: peer_timeout: 0 peer_credits: 0 peer_buffer_credits: 0 credits: 0 - net: tcp nid: 10.100.4.198@tcp status: up tunables: peer_timeout: 180 peer_credits: 8 peer_buffer_credits: 0 credits: 256 - net: tcp1 nid: 192.168.201.180@tcp1 status: up interfaces: 0: eth1 tunables: peer_timeout: 181 peer_credits: 8 peer_buffer_credits: 0 credits: 256 [root@eagle-54vm3 modprobe.d]# lnetctl route show -v [root@eagle-54vm3 modprobe.d]# </pre> </div></div> lustre-b2_7 build #29 LU-6340

DLC: /etc/rc.d/init.d/lnet doesn't configure lnet exactly as defined in lnet.conf

Bug Critical Resolved Fixed Amir Shehata Sarah Liu Fri, 6 Mar 2015 01:32:47 +0000 Sat, 16 Jan 2016 06:03:35 +0000 Mon, 6 Jul 2015 23:47:23 +0000 Lustre 2.7.0 Lustre 2.8.0 0 7 <p>Amir, can you please provide a patch, in case we have another 2.7 RC5.</p> <p>The issue here is that "lctl network up" is used to bring up LNet, but that configures everything in module parameters. The fix is to use lnetctl to configure LNet only if the proper lnet YAML configuration file is present. This way the script remains backward compatible.</p> <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/14000" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14000</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6340" title="DLC: /etc/rc.d/init.d/lnet doesn&#39;t configure lnet exactly as defined in lnet.conf" class="issue-link" data-issue-key="LU-6340"><del>LU-6340</del></a> lnet: LNet startup script fix<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: e3b4da8c93b7421802e3b8d03c6ef2b913eb56c5</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/14000/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/14000/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6340" title="DLC: /etc/rc.d/init.d/lnet doesn&#39;t configure lnet exactly as defined in lnet.conf" class="issue-link" data-issue-key="LU-6340"><del>LU-6340</del></a> lnet: LNet startup script fix<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: f7259a01bb3f18f571d6ed8ecf7c95e1f9521bbb</p> Duplicate LU-7474 Related Development Rank 1|hzx7tr: Rank (Obsolete) 17752 Severity