[LU-1089] lustre-b2_1 not building ko2iblnd Created: 09/Feb/12  Updated: 10/Feb/12  Resolved: 10/Feb/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.1.1
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Cliff White (Inactive) Assignee: Oleg Drokin
Resolution: Fixed Votes: 0
Labels: None
Environment:

Hyperion


Severity: 3
Rank (Obsolete): 6464

 Description   

wget http://build.whamcloud.com/job/lustre-b2_1/39/arch=x86_64,build_type=server,distro=el6,ib_stack=inkernel/artifact/artifacts/RPMS/x86_64/lustre-modules-2.1.1-2.6.32_220.el6_lustre.g4554b65.x86_64_g4554b65.x86_64.rpm
Resolving build.whamcloud.com... 69.226.2.25
Connecting to build.whamcloud.com|69.226.2.25|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 23659492 (23M) [application/x-rpm]
Saving to: `lustre-modules-2.1.1-2.6.32_220.el6_lustre.g4554b65.x86_64_g4554b65.x86_64.rpm'

100%[======================================>] 23,659,492 76.5K/s in 5m 17s

2012-02-09 17:35:44 (72.8 KB/s) - `lustre-modules-2.1.1-2.6.32_220.el6_lustre.g4554b65.x86_64_g4554b65.x86_64.rpm' saved [23659492/23659492]

  1. hyperion1 /home/white215/images/rhel6/2.1.1/server > ls
    lustre-modules-2.1.1-2.6.32_220.el6_lustre.g4554b65.x86_64_g4554b65.x86_64.rpm
    x86_64
    x86_64.zip
  2. hyperion1 /home/white215/images/rhel6/2.1.1/server > rpm -qlp lustre-modules-2.1.1-2.6.32_220.el6_lustre.g4554b65.x86_64_g4554b65.x86_64.rpm | grep lnd
    /lib/modules/2.6.32-220.el6_lustre.g4554b65.x86_64/updates/kernel/net/lustre/ksocklnd.ko
  3. hyperion1 /home/white215/images/rhel6/2.1.1/server >

ko2iblnd just ain't there. Makes it very hard to test on Hyperion.



 Comments   
Comment by Jian Yu [ 09/Feb/12 ]

This was introduced by:
LU-781 kernel: kernel update [RHEL6.2 2.6.32-220]

The ko2iblnd.ko was in http://build.whamcloud.com/job/lustre-b2_1/34/, but missed from http://build.whamcloud.com/job/lustre-b2_1/35/.

Comment by Oleg Drokin [ 09/Feb/12 ]

I checked the build log and the configure cannot find something when looking for o2ib.
Unfortunately we don't save the config.log, so no way to know it for now, I retriggered the build (#40), so hopefully somebody can grab the config.log from there

Comment by Brian Murrell (Inactive) [ 10/Feb/12 ]

It would appear that build #41 resolved this by landing LU-778. Cliff, please confirm and close if so.

Comment by Cliff White (Inactive) [ 10/Feb/12 ]

Tested new build, has o2iblnd

Comment by Christopher Morrone [ 10/Feb/12 ]

You can avoid this problem in the figure by configuring with "--with-o2ib=yes". Then it will be really obvious that something went wrong in detecting o2ib, because the build will abort rather than quietly leaving out needed support.

Generated at Sat Feb 10 01:13:24 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.