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-3617 Lustre <p>We ran into an issue at Yale recently where the Lustre servers all got RDMA_CM_EVENT_TIMEWAIT_EXIT, which the servers didn't recognize and LBUGed on. There are two problems here. The first is that configure clearly doesn't do the right thing anymore, and the second is that Lustre shouldn't LBUG if it gets those events, even if configure doesn't find them. </p> <p>I double checked on your build systems to make sure it wasn't just ours:<br/> <a href="http://build.whamcloud.com/job/lustre-b1_8/arch=x86_64,build_type=server,distro=el5,ib_stack=inkernel/258/consoleFull" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-b1_8/arch=x86_64,build_type=server,distro=el5,ib_stack=inkernel/258/consoleFull</a></p> <p>That's the official 1.8.9 build console if I'm not mistaken, and you can see:<br/> checking if OFED has RDMA_CM_EVENT_ADDR_CHANGE... no<br/> checking if OFED has RDMA_CM_EVENT_TIMEWAIT_EXIT... no</p> LU-3617

configure incorrectly finds no for RDMA events 14 and 15 on latest RHEL5

Bug Minor Resolved Duplicate Amir Shehata Kit Westneat mn8 patch Mon, 22 Jul 2013 20:52:25 +0000 Tue, 29 Oct 2013 00:44:22 +0000 Tue, 29 Oct 2013 00:23:52 +0000 Lustre 1.8.9 Lustre 1.8.9 0 10 <p>The patch we used:<br/> <a href="http://review.whamcloud.com/#/c/7079/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/7079/</a></p> <p>This looks like <a href="https://jira.whamcloud.com/browse/LU-3166" title="(o2iblnd_cb.c:2831:kiblnd_cm_callback()) LBUG" class="issue-link" data-issue-key="LU-3166"><del>LU-3166</del></a>. LBUG was used on unknown events because it's a serious situation - o2iblnd might not function properly if some unknown events are ignored.</p> <p>It's similar, but for RHEL in-kernel rdma instead of Mellanox. I think this shows just how fragile the configure test is. Are these tests even necessary anymore? It looks like the events were added over 5 years ago. At the very least, it seems like there should be some kind of acceptance test added to make sure that Intel releases always have support for these events. </p> <p>The logic for using LBUG still seems strange - because it might not function properly, you make sure that it doesn't function properly? It seems like an error message or something would be as effective. Events aren't added to OFED very often, right?</p> <p>Amir</p> <p>What is your view of this?</p> <p>Peter</p> <p>Yes, it might not work so we make sure it would not work. The consequences of ignoring unknown events are unknown, which might include data loss or corruption - we don't know, so better safe than sorry. Unknown events are supposed to happen ONLY when the o2iblnd is used with unsupported OFED release. In this case, the OFED/events are supported, it's the tests that were broken. I think the LBUG is fine - we should fix the tests, and make sure that such test failures won't happen again.</p> <p>It looks like this is RBEL 5. What version of RHEL, and what version of OFED?</p> <p>That is correct. It is RHEL 5.9, with the in-kernel RDMA. </p> <p>We just ran into this problem on our production systems. No detecting certain features can cause a Oops. I have a patch that fixes this problem at</p> <p><a href="http://review.whamcloud.com/#/c/7488" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/7488</a></p> <p>Sorry the patch points to the original ticket I filed.</p> <p>I'm seeing Lustre initialization errors in Maloo. The logs are not very informative so does anyone know what is going wrong?</p> <p>James, can you please look at the questions I just posted on Gerrit?</p> <p>Both test fail from the same thing.</p> <p>In file included from /data/buildsystem/jsimmons-widow/rpmbuild/BUILD/kernel-2.6.18/linux-2.6.18-348.3.1.el5.x86_64/<br/> include/rdma/rdma_cm.h:39,<br/> from /data/buildsystem/jsimmons-widow/rpmbuild/usr/src/lustre-1.8.9/build/conftest.c:43:<br/> /data/buildsystem/jsimmons-widow/rpmbuild/BUILD/kernel-2.6.18/linux-2.6.18-348.3.1.el5.x86_64/include/rdma/ib_addr.h<br/> : In function 'rdma_vlan_dev_vlan_id':<br/> /data/buildsystem/jsimmons-widow/rpmbuild/BUILD/kernel-2.6.18/linux-2.6.18-348.3.1.el5.x86_64/include/rdma/ib_addr.h<br/> :154: error: implicit declaration of function 'vlan_dev_vlan_id'</p> <p>-------------------------------------------------------------------------------------------------------------<br/> <span class="error">&#91;jsimmons@testbox linux-2.6.18-348.3.1.el5.widow.x86_64&#93;</span># grep -rl vlan_dev_vlan_id .<br/> ./include/rdma/ib_addr.h<br/> ./include/scsi/fc_compat.h</p> <p>So yes vlan_dev_vlan_id is located in fc_compact.h</p> <p>This is a duplicate of 3166, which tracks the same issue for release 2.5</p> <p>While the symptoms are the same, this is not the same issue. <a href="https://jira.whamcloud.com/browse/LU-3166" title="(o2iblnd_cb.c:2831:kiblnd_cm_callback()) LBUG" class="issue-link" data-issue-key="LU-3166"><del>LU-3166</del></a> is configuration issues with OFED-3.5, this one is for RHEL's in-kernel OFED. I think it should be reopened as the solution is going to be different. </p> Development Rank 1|hzvvuf: Rank (Obsolete) 9298 Severity