[Lustre-discuss] Build lustre 2.6 Client on Debian Wheezy

[Thierry Lamoureux]

Hi,

I went further on my problem. I am still wanted to install lustre client module to a debian wheezy unpatched kernel.

Now the last step is working, it generates me the package :
lustre-client-modules-3.2.63-wheezy-client_2.6.0.0_amd64.deb

But I didn't know where the "3.2.63" came from.

When I list the packages I've installed I got :
# Dpkg --list |grep linux
ii  linux-headers-3.2.0-4-all-amd64            3.2.65-1+deb7u1               amd64        All header files for Linux 3.2 (meta-package)
ii  linux-headers-3.2.0-4-amd64                3.2.65-1+deb7u1               amd64        Header files for Linux 3.2.0-4-amd64
ii  linux-headers-3.2.0-4-common               3.2.65-1+deb7u1               amd64        Common header files for Linux 3.2.0-4
ii  linux-headers-3.2.0-4-common-rt            3.2.65-1+deb7u1               amd64        Common header files for Linux 3.2.0-4-rt
ii  linux-headers-3.2.0-4-rt-amd64             3.2.65-1+deb7u1               amd64        Header files for Linux 3.2.0-4-rt-amd64
ii  linux-image-3.2.0-4-amd64                  3.2.65-1+deb7u1               amd64        Linux 3.2 for 64-bit PCs
ii  linux-image-amd64                          3.2+46                        amd64        Linux for 64-bit PCs (meta-package)
ii  linux-kbuild-3.2                           3.2.17-1                      amd64        Kbuild infrastructure for Linux 3.2
ii  linux-libc-dev:amd64                       3.2.65-1+deb7u1               amd64        Linux support headers for userspace development
ii  linux-source                               3.2+46                        all          Linux kernel source (meta-package)
ii  linux-source-3.2                           3.2.65-1+deb7u1               all          Linux kernel source for version 3.2 with Debian patches

By the way, I've installed this package. Files are installed in the folder /lib/mobules/3.2.63-wheezy-client instead of /lib/modules/3.2.0-4-amd64, which is the normal path of my unpatched kernel modules.

So of course, when I tried to make a modprobe, I got the following answer :
# modprobe lustre
FATAL: Module lustre not found.

I tried to transfer the files to the /lib/modules/3.2.0-4-amd64 folder and then the return message is :
# modprobe -v lustre
insmod /lib/modules/3.2.0-4-amd64/kernel/net/lustre/libcfs.ko 
ERROR: could not insert 'lustre': Exec format error

If I tried to insert manually the lustre.ko module, I got the same message.

It would be great if some of you have an idea.

Regards,

Thierry.

-----Message d'origine-----
De : E.S. Rosenberg [mailto:esr+lustre at mail.hebrew.edu] 
Envoyé : dimanche 11 janvier 2015 10:52
À : Thierry Lamoureux
Cc : Dilger, Andreas; Kilian Cavalotti; lustre-discuss at lists.lustre.org
Objet : Re: [Lustre-discuss] Build lustre 2.6 Client on Debian Wheezy

On Fri, Jan 9, 2015 at 12:45 PM, Thierry Lamoureux <thierry.lamoureux at noveltis.fr> wrote:
> Hi guys,
>
> Did one of you had a little moment to have a look to my previous message?
As far as I can tell your previous message is not a complete paste, it doesn't end at an error and it seems to end in the middle of some output.
If you have the ability I would suggest using a newer kernel where you can use the built-in kernel module instead of having to build your own (at what version of lustre is the kernel.org version of lustre?) Regards, Eli
>
> Regards,
>
> Thierry L.
>
> -----Message d'origine-----
> De : lustre-discuss-bounces at lists.lustre.org 
> [mailto:lustre-discuss-bounces at lists.lustre.org] De la part de Thierry 
> Lamoureux Envoyé : mercredi 7 janvier 2015 17:15 À : Dilger, Andreas; 
> Kilian Cavalotti Cc : lustre-discuss at lists.lustre.org Objet : Re: 
> [Lustre-discuss] Build lustre 2.6 Client on Debian Wheezy
>
> Hi,
>
> Thanks for your replies. I tried Kilian's advice and it going further, but it is still not work.
>
> You can see the result of make-kpkg here : 
> http://pastebin.com/9E0gDGve
>
> It looks like it doesn't found any module to build even if I've 
> correctly configure MODULE_LOC variable according to this example : 
> http://lists.lustre.org/pipermail/lustre-discuss/2014-May/017734.html
>
> It would be great if someone have another idea.
>
> Thank you,
>
> Thierry.
>
> -----Message d'origine-----
> De : Dilger, Andreas [mailto:andreas.dilger at intel.com] Envoyé : 
> mercredi 7 janvier 2015 12:43 À : Kilian Cavalotti; Thierry Lamoureux 
> Cc : lustre-discuss at lists.lustre.org Objet : Re: [Lustre-discuss] 
> Build lustre 2.6 Client on Debian Wheezy
>
> On 2015/01/07, 4:33 AM, "Kilian Cavalotti"
> <kilian.cavalotti.work at gmail.com> wrote:
>
>>Bonjour Thierry,
>>
>>> /bin/sh: 1: [: -lt: unexpected operator
>>
>>I'm pretty sure that's because in Debian, /bin/sh is linked to dash 
>>and the Lustre build script expects bash.
>>
>>You can try to run:
>># dpkg-reconfigure dash
>>choose No to link /bin/sh to bash, and re-run the make-kpkg part.
>>Hopefully it will work better.
>>
>>I suggest to re-run "dpkg-reconfigure dash" afterwards to restore dash 
>>as the default shell.
>
> Which script is under discussion here?  Definitely we've assumed bash is available, and use bashisms heavily in the testing scripts, since bash is standard on Linux.
>
> If there are are a limited number of places where /bin/sh is assumed to be /bin/bash then it makes sense to fix them so that Debian builds work without users having to change their config.  Is this just a matter of using "#!/bin/bash" explicitly in these scripts, or should they be changed to conform to POSIX sh behaviour?
>
> Cheers, Andreas
> --
> Andreas Dilger
>
> Lustre Software Architect
> Intel High Performance Data Division
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss