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-14297 Lustre <p>Hello, I am trying to install lustre on our lnet routers which have connectx-5 cards installed in them using dkms on Centos 7.8 with kernel 3.10.0-1127.19.1.el7.x86_64. Also Mellanox just released their latest driver version OFED-5.2-1.0.4 yesterday Jan 4, 2021. When dkms tries to compile lustre, it fails with the following at end:</p> <p>configure: LNet kernel checks<br/> ==============================================================================<br/> checking whether to enable CPU affinity support... yes<br/> checking if Linux kernel has cpu affinity support... yes<br/> checking whether to enable tunable backoff TCP support... yes<br/> checking if Linux kernel has tunable backoff TCP support... no<br/> checking whether to use Compat RDMA... /bin/ofed_info<br/> no<br/> configure: error: no OFED nor kernel OpenIB gen2 headers present<br/> configure error, check /var/lib/dkms/lustre-client/2.12.5/build/config.log</p> <p>Building module:<br/> cleaning build area...(bad exit status: 2)<br/> make -j8 KERNELRELEASE=3.10.0-1127.19.1.el7.x86_64...(bad exit status: 2)<br/> Error! Bad return status for module build on kernel: 3.10.0-1127.19.1.el7.x86_64 (x86_64)<br/> Consult /var/lib/dkms/lustre-client/2.12.5/build/make.log for more information.</p> <p>Also, I did verify that the MLNX rpms that are supposed to be installed, are installed.<br/> On the machine I am trying to install on, I did check and ibstat states that both the cards have an active LinkUP:</p> <p><span class="error">&#91;root@lnet08 ~&#93;</span># ibstat<br/> CA 'mlx5_0'<br/> CA type: MT4119<br/> Number of ports: 1<br/> Firmware version: 16.26.1040<br/> Hardware version: 0<br/> Node GUID: 0xb8599f03002f8318<br/> System image GUID: 0xb8599f03002f8318<br/> Port 1:<br/> State: Active<br/> Physical state: LinkUp<br/> Rate: 100<br/> Base lid: 1522<br/> LMC: 0<br/> SM lid: 1434<br/> Capability mask: 0x2651e848<br/> Port GUID: 0xb8599f03002f8318<br/> Link layer: InfiniBand<br/> CA 'mlx5_1'<br/> CA type: MT4119<br/> Number of ports: 1<br/> Firmware version: 16.26.1040<br/> Hardware version: 0<br/> Node GUID: 0xb8599f03002f8319<br/> System image GUID: 0xb8599f03002f8318<br/> Port 1:<br/> State: Active<br/> Physical state: LinkUp<br/> Rate: 56<br/> Base lid: 2260<br/> LMC: 0<br/> SM lid: 158<br/> Capability mask: 0x2651e848<br/> Port GUID: 0xb8599f03002f8319<br/> Link layer: InfiniBand</p> <p>Any ideas how to get this to work ?</p> <p>Thanks,<br/> Mike</p> Dell and Lenovo hardware. MLNX OFED-5.2-1.0.4. Lustre 2.12.5. OS is Centos 7.8. Kernel is 3.10.0-1127.19.1.el7.x86_64 LU-14297

Can't compile lustre client against MLNX OFED-5.2-1.0.4 on Centos 7.8

Bug Major Resolved Fixed Jian Yu Michael Ethier Wed, 6 Jan 2021 01:04:59 +0000 Tue, 23 Jan 2024 08:15:33 +0000 Tue, 23 Jan 2024 08:15:33 +0000 Lustre 2.12.5 Lustre 2.12.7 0 6 <p>Jian</p> <p>Could you please investigate?</p> <p>Thanks</p> <p>Peter</p> <p>Hi Mike,</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>checking whether to use Compat RDMA... /bin/ofed_info no configure: error: no OFED nor kernel OpenIB gen2 headers present configure error, check /var/lib/dkms/lustre-client/2.12.5/build/config.log </pre> </div></div> <p>Could you please upload the <tt>config.log</tt> to this ticket for investigation?</p> <p>Hi sure its attached.<br/> Thanks,<br/> Mike<br/> <span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/37106/37106_config.log" title="config.log attached to LU-14297">config.log^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span> </p> <p>Hi Mike,</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> o2ib_found=false for O2IBPATH in $O2IBPATHS; do AS_IF([test \( -f ${O2IBPATH}/include/rdma/rdma_cm.h -a \ -f ${O2IBPATH}/include/rdma/ib_cm.h -a \ -f ${O2IBPATH}/include/rdma/ib_verbs.h -a \ -f ${O2IBPATH}/include/rdma/ib_fmr_pool.h \)], [ o2ib_found=true break ]) done </pre> </div></div> <p>Could you please check if the above header files are located under <tt>/usr/src/ofa_kernel/default</tt>?</p> <p>Hi Jian,<br/> This is what I found:<br/> <span class="error">&#91;root@cannonlnet08 ~&#93;</span># cd /usr/src/ofa_kernel/default<br/> <span class="error">&#91;root@cannonlnet08 default&#93;</span># find . -name rdma_cm.h -print<br/> ./include/rdma/rdma_cm.h<br/> <span class="error">&#91;root@cannonlnet08 default&#93;</span># find . -name ib_verbs.h -print<br/> ./include/rdma/ib_verbs.h<br/> <span class="error">&#91;root@cannonlnet08 default&#93;</span># find . -name ib_fmr_pool.h -print<br/> <span class="error">&#91;root@cannonlnet08 default&#93;</span># </p> <p>Looks like ib_fmr_pool.h is missing ?</p> <p><span class="error">&#91;root@cannonlnet08 default&#93;</span># cd ./include/rdma<br/> <span class="error">&#91;root@cannonlnet08 rdma&#93;</span># ls<br/> ib_addr.h ib_hdrs.h ib_sa.h ib_verbs.h lag.h opa_vnic.h rdma_netlink.h restrack.h uverbs_named_ioctl.h<br/> iba.h ib_mad.h ib_smi.h ib_verbs_nvmf_def.h mr_pool.h peer_mem.h rdmavt_cq.h rw.h uverbs_std_types.h<br/> ib_cache.h ib_marshall.h ibta_vol1_c12.h ib_verbs_nvmf.h opa_addr.h rdma_cm.h rdma_vt.h signature.h uverbs_types.h<br/> ib_cm.h ib_pack.h ib_umem.h iw_cm.h opa_port_info.h rdma_cm_ib.h rdmavt_mr.h tid_rdma_defs.h<br/> ib.h ib_pma.h ib_umem_odp.h iw_portmap.h opa_smi.h rdma_counter.h rdmavt_qp.h uverbs_ioctl.h</p> <p>Thanks,<br/> Mike</p> <p>Yes, Mike. If one or more of those files is missing, then configure will return "error: no OFED nor kernel OpenIB gen2 headers present".<br/> The files are usually included in mlnx-ofa_kernel-devel rpm. It seems ib_fmr_pool.h is missing from MLNX_OFED 5.2-1.0.4.0. Let me investigate further.</p> <p>Can you try patch <a href="https://review.whamcloud.com/#/c/40287" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/40287</a></p> <p>Hi James, can you point me to the procedure to apply the patch ?<br/> Thanks, Mike</p> <p>Is the the procedure ? I would run without --dryrun to implement the changes.</p> <p><span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># pwd<br/> /usr/src/lustre-client-2.12.5<br/> <span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># patch -p1 --dry-run &lt; ~/14b20ca6.diff<br/> checking file lnet/autoconf/lustre-lnet.m4<br/> Hunk #1 succeeded at 157 (offset 48 lines).<br/> Hunk #2 succeeded at 234 (offset 48 lines).<br/> Hunk #3 succeeded at 567 with fuzz 2 (offset 25 lines).<br/> checking file lnet/klnds/o2iblnd/o2iblnd.c<br/> Hunk #1 succeeded at 1469 (offset 56 lines).<br/> Hunk #2 succeeded at 1528 (offset 56 lines).<br/> Hunk #3 succeeded at 1557 (offset 56 lines).<br/> Hunk #4 succeeded at 1566 (offset 56 lines).<br/> Hunk #5 succeeded at 1675 (offset 56 lines).<br/> Hunk #6 succeeded at 1767 (offset 57 lines).<br/> Hunk #7 succeeded at 1789 (offset 57 lines).<br/> Hunk #8 succeeded at 1799 (offset 57 lines).<br/> Hunk #9 succeeded at 1813 (offset 57 lines).<br/> Hunk #10 succeeded at 1855 (offset 57 lines).<br/> Hunk #11 succeeded at 1871 (offset 57 lines).<br/> Hunk #12 succeeded at 1894 (offset 57 lines).<br/> Hunk #13 FAILED at 1885.<br/> Hunk #14 succeeded at 1960 (offset 57 lines).<br/> Hunk #15 succeeded at 1987 (offset 57 lines).<br/> Hunk #16 succeeded at 2586 (offset -21 lines).<br/> Hunk #17 succeeded at 2600 (offset -21 lines).<br/> 1 out of 17 hunks FAILED<br/> checking file lnet/klnds/o2iblnd/o2iblnd.h<br/> Hunk #1 succeeded at 71 (offset -12 lines).<br/> Hunk #2 succeeded at 174 (offset -7 lines).<br/> Hunk #3 succeeded at 337 with fuzz 2 (offset -13 lines).<br/> Hunk #4 FAILED at 388.<br/> 1 out of 4 hunks FAILED<br/> checking file lnet/klnds/o2iblnd/o2iblnd_cb.c<br/> Hunk #3 succeeded at 625 (offset -1 lines).<br/> Hunk #4 succeeded at 656 (offset -1 lines).<br/> Hunk #5 succeeded at 687 (offset -1 lines).</p> <p>Hi Mike,<br/> I'm back-porting the patch to Lustre 2.12.5 and will share it with you.<br/> BTW, it turns out ib_fmr_pool.h exists in kernel-devel-3.10.0-1127.19.1.el7:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># rpm -qlp kernel-devel-3.10.0-1127.19.1.el7.x86_64.rpm | grep ib_fmr_pool.h /usr/src/kernels/3.10.0-1127.19.1.el7.x86_64/include/rdma/ib_fmr_pool.h </pre> </div></div> <p>While installing MLNX_OFED 5.2-1.0.4.0 on the node, did you pass "--add-kernel-support" option to mlnxofedinstall or run mlnx_add_kernel_support.sh to generate an MLNX_OFED package with drivers for the kernel 3.10.0-1127.19.1.el7 on the node?</p> <p>Hi Jian,<br/> Yes I ran mlnx_add_kernel_support.sh to generate an MLNX_OFED package with drivers for the kernel 3.10.0-1127.19.1.el7 on the node. Then I took the resulting .gz file and extracted the RPMS from it, and used them to install MLNX OFED on this node via the yum repo method.<br/> Thanks,<br/> Mike</p> <p>Thank you Mike for the info.<br/> Here is the back-ported patch for Lustre 2.12.5: <a href="https://review.whamcloud.com/41153" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/41153</a>. You can apply the patch and build manually or wait for Jenkins build to be finished.</p> <p>Hi Jian,<br/> I applied your patch and tried to build lustre 2.12.5 client and it failed the same way:<br/> <span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># patch -p1 &lt; ~/f4d9b03a.diff<br/> patching file lnet/autoconf/lustre-lnet.m4<br/> patching file lnet/klnds/o2iblnd/o2iblnd.c<br/> patching file lnet/klnds/o2iblnd/o2iblnd.h<br/> patching file lnet/klnds/o2iblnd/o2iblnd_cb.c</p> <p><span class="error">&#91;root@cannonlnet08 ~&#93;</span># dkms install -k $(uname -r) lustre-client/2.12.5</p> <p>Kernel preparation unnecessary for this kernel. Skipping...</p> <p>Running the pre_build script:<br/> checking build system type... x86_64-unknown-linux-gnu<br/> checking host system type... x86_64-unknown-linux-gnu<br/> ...<br/> ...<br/> configure: LNet kernel checks<br/> ==============================================================================<br/> checking whether to enable CPU affinity support... yes<br/> checking if Linux kernel has cpu affinity support... yes<br/> checking whether to enable tunable backoff TCP support... yes<br/> checking if Linux kernel has tunable backoff TCP support... no<br/> checking whether to use Compat RDMA... /bin/ofed_info<br/> no<br/> configure: error: no OFED nor kernel OpenIB gen2 headers present<br/> configure error, check /var/lib/dkms/lustre-client/2.12.5/build/config.log</p> <p>Building module:<br/> cleaning build area...(bad exit status: 2)<br/> make -j8 KERNELRELEASE=3.10.0-1127.19.1.el7.x86_64...(bad exit status: 2)<br/> Error! Bad return status for module build on kernel: 3.10.0-1127.19.1.el7.x86_64 (x86_64)<br/> Consult /var/lib/dkms/lustre-client/2.12.5/build/make.log for more information.</p> <p>Hi Mike,<br/> I'm setting up a test node to reproduce the issue and verify the patch.</p> <p>Hi Mike,<br/> I can reproduce the ib_fmr_pool.h missing issue on my test node. However, with patch <a href="https://review.whamcloud.com/41153" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/41153</a> applied to Lustre 2.12.5, the issue was resolved. I installed the el7.8/x86_64 lustre-client-dkms rpm from Jenkins build <a href="https://build.whamcloud.com/job/lustre-reviews/78554/" class="external-link" target="_blank" rel="nofollow noopener">https://build.whamcloud.com/job/lustre-reviews/78554/</a> :</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># rpm -ivh lustre-client-dkms-2.12.5_1_gf4d9b03-1.el7.noarch.rpm Preparing... ################################# [100%] Updating / installing... 1:lustre-client-dkms-2.12.5_1_gf4d9################################# [100%] Loading new lustre-client-2.12.5_1_gf4d9b03 DKMS files... Building for 3.10.0-1127.19.1.el7.x86_64 Building initial module for 3.10.0-1127.19.1.el7.x86_64 &lt;~snip~&gt; </pre> </div></div> <p>The config.log showed that:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>configure:18577: checking whether to use Compat RDMA configure:18673: result: yes configure:18708: checking whether to use any OFED backport headers configure:18716: result: no configure:18725: checking whether to enable OpenIB gen2 support &lt;~snip~&gt; configure:18794: result: yes configure:18817: adding /usr/src/ofa_kernel/default/Module.symvers to Symbol Path </pre> </div></div> <p><tt>configure</tt> passed.</p> <p>After <tt>configure</tt> passed, building the codes hit the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>/var/lib/dkms/lustre-client/2.12.5_1_gf4d9b03/build/lnet/klnds/o2iblnd/o2iblnd_cb.c: In function ‘kiblnd_reject’: /var/lib/dkms/lustre-client/2.12.5_1_gf4d9b03/build/lnet/klnds/o2iblnd/o2iblnd_cb.c:2421:9: error: too few arguments to function ‘rdma_reject’ rc = rdma_reject(cmid, rej, sizeof(*rej)); ^ </pre> </div></div> <p>The error has been fixed in patch <a href="https://review.whamcloud.com/39781" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/39781</a> and landed for Lustre 2.12.6.</p> <p>With patch <a href="https://review.whamcloud.com/41152" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/41152</a> applied to Lustre 2.12.6, I can successfully build Lustre 2.12.6 client on CentOS 7.8 with kernel 3.10.0-1127.19.1.el7.x86_64 and MLNX_OFED 5.2-1.0.4.0:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># rpm -ivh lustre-client-dkms-2.12.6_1_g14e02fb-1.el7.noarch.rpm Preparing... ################################# [100%] Updating / installing... 1:lustre-client-dkms-2.12.6_1_g14e0################################# [100%] Loading new lustre-client-2.12.6_1_g14e02fb DKMS files... Building for 3.10.0-1127.19.1.el7.x86_64 Building initial module for 3.10.0-1127.19.1.el7.x86_64 Done. &lt;~snip~&gt; ko2iblnd.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.10.0-1127.19.1.el7.x86_64/extra/ &lt;~snip~&gt; Adding any weak-modules depmod.... DKMS: install completed. </pre> </div></div> <p>Hi Jian,</p> <p>Thanks for the feedback. However, we are running Lustre client 2.12.5 almost everywhere on our production infrastructure.</p> <p>I am working currently on updating out LNET routers from Centos 7.7 Lustre 2.12.4 and OFED-4.7-1.0.0 to Centos 7.8 and was hoping to keep the lustre version the same (ie 2.12.5).</p> <p>Based on your info I have to use lustre 2.12.6 in order to get this to work with the latest MLNX OFED. And Mellanox recommends I use their latest OFED version. Do you know of any compatibility issues or other issues updating our LNET routers to 2.12.6 ? Or should I just leave them alone as they seem to be working fine.</p> <p>Thanks,<br/> Mike</p> <p>Hi Mike,<br/> There are some LNet fixups and improvements in Lustre 2.12.6, but I'm not sure if there are compatibility issues.<br/> I just verified that with the following two patches applied to Lustre 2.12.5, the client build also passed on CentOS 7.8 with kernel 3.10.0-1127.19.1.el7.x86_64 and MLNX_OFED 5.2-1.0.4.0:</p> <ul class="alternate" type="square"> <li><a href="https://review.whamcloud.com/41152" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/41152</a> "<a href="https://jira.whamcloud.com/browse/LU-13783" title="Support for linux kernel version 5.8" class="issue-link" data-issue-key="LU-13783"><del>LU-13783</del></a> o2iblnd: make FMR-pool support optional."</li> <li><a href="https://review.whamcloud.com/39781" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/39781</a> "<a href="https://jira.whamcloud.com/browse/LU-13761" title="MOFED 5.1 support" class="issue-link" data-issue-key="LU-13761"><del>LU-13761</del></a> o2ib: Fix compilation with MOFED 5.1"</li> </ul> <p>Hi Jian,<br/> Thanks you have been very responsive in regards to my issue. I will see if I can make this work.<br/> Mike</p> <p>BTW, do you know when this issue will be fixed in the general lustre release ? 2.12.6 is already released.</p> <p>Hi Jian,<br/> I just tried those 2 patches you recommended to lustre 2.12.5 and its failing the same way still. How exactly are you applying those 2 patches ? This is what I did:</p> <p><span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># pwd<br/> /usr/src/lustre-client-2.12.5<br/> <span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># patch -p1 &lt; ~/14e02fb3.diff<br/> patching file lnet/autoconf/lustre-lnet.m4<br/> Hunk #3 succeeded at 567 with fuzz 2 (offset -23 lines).<br/> patching file lnet/klnds/o2iblnd/o2iblnd.c<br/> patching file lnet/klnds/o2iblnd/o2iblnd.h<br/> patching file lnet/klnds/o2iblnd/o2iblnd_cb.c<br/> <span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># patch -p1 &lt; ~/ba702c79.diff<br/> patching file lnet/autoconf/lustre-lnet.m4<br/> Hunk #1 succeeded at 579 with fuzz 2 (offset 9 lines).<br/> patching file lnet/klnds/o2iblnd/o2iblnd_cb.c<br/> Hunk #1 succeeded at 2418 (offset 11 lines).</p> <p>Then I started the build:<br/> <span class="error">&#91;root@cannonlnet08 lustre-client-2.12.5&#93;</span># dkms install -k $(uname -r) lustre-client/2.12.5</p> <p>Kernel preparation unnecessary for this kernel. Skipping...</p> <p>Running the pre_build script:<br/> checking build system type... x86_64-unknown-linux-gnu<br/> ...<br/> ...</p> <p>You're welcome, Mike. I'm not sure when the next 2.12.x version will be released.<br/> I directly installed the lustre-client-dkms rpm generated by Jenkins build system <a href="https://build.whamcloud.com/job/lustre-reviews/78580/arch=x86_64,build_type=client,distro=el7.8,ib_stack=inkernel/artifact/artifacts/RPMS/x86_64/lustre-client-dkms-2.12.5_1_g726eed2-1.el7.noarch.rpm" class="external-link" target="_blank" rel="nofollow noopener">https://build.whamcloud.com/job/lustre-reviews/78580/arch=x86_64,build_type=client,distro=el7.8,ib_stack=inkernel/artifact/artifacts/RPMS/x86_64/lustre-client-dkms-2.12.5_1_g726eed2-1.el7.noarch.rpm</a> without problem.<br/> I will try your method to see how it goes. </p> <p>Hi Jian,<br/> Any luck in trying my method ?<br/> Thanks,<br/> Mike</p> <p>My suggestion is that we expedite landing <a href="https://review.whamcloud.com/#/c/41152/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/41152/</a> to b2_12 and then the tip of b2_12 will be what is needed to to build 2.12.6 for MOFED 5.2. We have not thought about 2.12.7 timing yet, but we will certainly want to include this fix.</p> <p>So I have an lnet router out of service that I was trying to get running with the latest MOFED and lustre 2.12.5. Should I just rebuilt it back to its previous functioning setup ? I don't want to leave it down for a long time.</p> <p>Hi Mike,<br/> I can reproduce your issue. After applying the patches, could you please run the attached <span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/37150/37150_autogen.sh" title="autogen.sh attached to LU-14297">autogen.sh^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span> under <tt>/usr/src/lustre-client-2.12.5</tt> before running <tt>dkms install ...</tt>?</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># pwd /usr/src/lustre-client-2.12.5 # sh ./autogen.sh </pre> </div></div> <p>And before running <tt>autogen.sh</tt>, the attached <span class="nobr"><a href="https://jira.whamcloud.com/secure/attachment/37152/37152_lustre-version.m4" title="lustre-version.m4 attached to LU-14297">lustre-version.m4^{<img class="rendericon" src="https://jira.whamcloud.com/images/icons/link_attachment_7.gif" height="7" width="7" align="absmiddle" alt="" border="0"/>}</a></span> also needs to be put into <tt>/usr/src/lustre-client-2.12.5/config</tt>.<br/> The following steps work for me from scratch:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># rpm -ivh lustre-client-dkms-2.12.5-1.el7.noarch.rpm # cd /usr/src/lustre-client-2.12.5/ # patch -p1 &lt; /root/0001-LU-13761-o2ib-Fix-compilation-with-MOFED-5.1.patch # patch -p1 &lt; /root/0001-LU-13783-o2iblnd-make-FMR-pool-support-optional.patch # cp /root/autogen.sh . # cp /root/lustre-version.m4 config/ # sh ./autogen.sh # dkms install -k $(uname -r) lustre-client/2.12.5 ... ... - Installation - Installing to /lib/modules/3.10.0-1127.19.1.el7.x86_64/extra/ Adding any weak-modules depmod.... DKMS: install completed. </pre> </div></div> <p>Hi Jian,<br/> The patches I should apply are they the same ones or different ones ? Can you give me pointers to them ?<br/> Thanks,<br/> Mike</p> <p>Hi Mike,<br/> The same ones as those in <a href="https://jira.whamcloud.com/browse/LU-14297?focusedCommentId=288967&amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-288967" class="external-link" rel="nofollow">#comment-288967</a></p> <p>Hi Jian,<br/> I followed your instructions and that seems to have worked and the lnet route is running. I need to rebuild 9 other lnet routers and this is what I should correct ? Or is there going to be an "official" release that will include this fix soon ?<br/> It won't be an official version of 2.12.5 correct ?<br/> Thanks,<br/> Mike</p> <p>Mike</p> <p>The "official" release will be 2.12.7 but we don't have an exact timeline for it yet</p> <p>Peter</p> <p>Peter, our group is going to wait for 2.12.7 to be release before we update all our lnet routers. Do you think the 2.12.7 will be released in weeks or months ? Thanks.</p> <p>Michael</p> <p>It's possible something new might come to light that quickly changes this but, as things stand today, my best guess is months.</p> <p>Peter</p> Related LU-13783 LU-13761 Development Epic/Theme MLNX OFED-5.2-1.0.4 lustre-2.12.5 Rank 1|i01ilj: Rank (Obsolete) 9223372036854775807 Severity