[LU-956] lustre-2.1 /etc/init.d/lustre failed on sles11sp1

• Status: Closed
• Project: Lustre
• Affects Version/s: Lustre 2.1.0
• Type: Bug
• Priority: Major
• Reporter: Jay Lan (Inactive)
• Assignee: Zhenyu Xu
• Resolution: Cannot Reproduce

Environment

sles11sp1 2.6.32.23-0.3.1

• Severity: 2

Description

/etc/init.d/lustre of lustre-2.1 client tried to execute /etc/rc.d/init.d/functions.
There is no such file in sles11sp1.

Comments

[Peter Jones]

Yangsheng

Can you plese look into this issue?

Thanks

Peter

[Brian Murrell (Inactive)]

Jay,

Can you provide the output of:

# rpm -qif /etc/init.d/lustre

[Jay Lan (Inactive)]

Hi Brian,

node331 /etc/init.d # rpm -qif /etc/init.d/lustre
Name : lustre Relocations: (not relocatable)
Version : 2.1.0 Vendor: (none)
Release : 1.1nasC_ofed153_2.6.32.23_0.3.1.20110428_nasa Build Date: Fri Dec 30 15:05:10 2011
Install Date: Fri Dec 30 15:16:26 2011 Build Host: gulag1
Group : Utilities/System Source RPM: lustre-2.1.0-1.1nasC_ofed153_2.6.32.23_0.3.1.20110428_nasa.src.rpm
Size : 3923078 License: GPL
Signature : (none)
URL : http://wiki.whamcloud.com/
Summary : Lustre File System
Description :
Userspace tools and files for the Lustre file system.
Distribution: (none)
node331 /etc/init.d #

The git repo is available at
https://github.com/jlan/lustre-nas/tree/nas-2.1.0

[Jay Lan (Inactive)]

The change I made to the 1.1nasC vs 1nasC as in github repo was due to LU-955 I filed earlier:

diff --git a/lustre.spec.in b/lustre.spec.in
index 7223a90..c515731 100644
— a/lustre.spec.in
+++ b/lustre.spec.in
@@ 80,9 +80,6 @@ Requires: kernel%

{flavor}

Requires: kernel = %

{krequires}

%endif
%endif
-%if ! %

{is_client}

-Requires: lustre-backend-fs
-%endif
Group: Development/Kernel

%description modules

[Peter Jones]

Bobi

YangSheng is rather busy atm so could you please look at this one?

Thanks

Peter

[Brian Murrell (Inactive)]

Jay,

/etc/init.d/lustre appears to have been added by 925e52c295bfe24eca431a90b65a1aba28beda8b in your github repo. That appears to be an implementation of the patch for LU-107. We have not landed LU-107 to our tree yet so you must be getting this patch from some other source.

Ultimately this looks like a portability bug in that patch. Probably the file it's looking for only exists on RH based systems and not SUSE systems.

[Jay Lan (Inactive)]

Hmm, it was cherry-picked from LLNL's 2.1 git tree at github.

I was asked to review commits off LLNL's 2.1 git tree. That one seemed to be safe
to me back then.
Next time I will compare my version with your trees first.

Thanks for investigation and quick reply. Please close this ticket.

[Christopher Morrone]

Additionally, /etc/init.d/lustre is only used on servers. Is it causing any trouble on boot of the clients? We would want to know that.

[Peter Jones]

Jay

As I have said before, I really advise starting without any patches and only adding those you absolutely need.

Peter

[Brian Murrell (Inactive)]

Resolve per reporter.

[Jay Lan (Inactive)]

Christopher,

Our production machines run 1.8.6 clients and 1.8.6 servers mostly. Only one Lustre FS runs 2.1.

I was asked to set up a new test cluster to run acc-sm to test 2.1. My initial setup was 2.1 servers and 2.1 sles11sp1 clients. The 1.8.x rpms do not ship an /etc/init.d/lustre. Our site provides our own version. Without much thinking, i tried to execute /etc/init.d/lustre at sles11sp1 client and it failed at very beginning.

I was told then to work on 2.1 servers + 1.8.6 clients as priority. I would let you know if I find more problem in sles11sp1 client when I get back to that.

Jay