[LU-3043] server build for sles11sp2 is broken Created: 27/Mar/13  Updated: 08/Apr/13  Resolved: 08/Apr/13

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

Type: Bug Priority: Minor
Reporter: Bob Glossman (Inactive) Assignee: Bob Glossman (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

sles11sp2


Issue Links:
Related
is related to LU-1812 3.6/FC18 Server Patches Resolved
is related to LU-3337 enable server builds for sles11sp2 Resolved
Severity: 3
Rank (Obsolete): 7433

 Description   

While building with the latest recipe for sles11sp2 server from LU-1812, I discovered a new build failure. Errors look like:

  CC [M]  /home/bogl/lustre-release/lustre/mdt/mdt_handler.o
cc1: warnings being treated as errors
/home/bogl/lustre-release/lustre/mdt/mdt_handler.c: In function ‘mdt_path_current’:
/home/bogl/lustre-release/lustre/mdt/mdt_handler.c:5550: error: ‘rc’ may be used uninitialized in this function
make[6]: *** [/home/bogl/lustre-release/lustre/mdt/mdt_handler.o] Error 1
make[5]: *** [/home/bogl/lustre-release/lustre/mdt] Error 2
make[4]: *** [/home/bogl/lustre-release/lustre] Error 2
make[3]: *** [_module_/home/bogl/lustre-release] Error 2
make[3]: Leaving directory `/home/bogl/linux-3.0.58-0.6.6'
make[2]: *** [modules] Error 2
make[2]: Leaving directory `/home/bogl/lustre-release'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bogl/lustre-release'
make: *** [all] Error 2

I believe this failure came from code added in recent commit a19f706ebef23a5778572553256df78abb81e1a4, LU-2801 mdt: checking remote object in mdt_swap_layouts. It isn't an issue in normal lustre builds in Centos. It hasn't been seen in routine lustre builds for sles11sp2 since those are currently client only.

I will push a trivial patch for this soon.



 Comments   
Comment by Bob Glossman (Inactive) [ 27/Mar/13 ]

http://review.whamcloud.com/5854

Comment by James A Simmons [ 08/Apr/13 ]

Landed to master. Ticket can be closed.

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