On Thu, 2010-07-08 at 11:54 +0200, Alessandro Luccaroni - Diennea wrote: > > [r...@lustreclient2 src]# uname -r > 2.6.18-164.el5
We have never (directly[1]) supported this particular kernel revision. It looks rather old and likely we have supported an updated revision of it. Currently I see that we have packages for kernels: 2.6.18_164.6.1.0.1.el5 (1.8.2 on OEL5) 2.6.18_164.11.1.el5 (1.8.2 on RHEL5) 2.6.18_164.11.1.0.1.el5 (1.8.3 on OEL5) 2.6.18_164.11.1.el5 (1.8.3 on RHEL5) > [r...@lustreclient2 mnt]# ls -l /lib/modules/ > drwxr-xr-x 6 root root 4096 Jul 7 17:57 2.6.18-164.11.1.0.1.el5 > drwxr-xr-x 6 root root 4096 Jul 7 17:58 2.6.18-164.el5 > > I think the problem is the different kernel revision, but i can't find > on the Red Hat Network the 2.6.18_164.11.1.0.1.el5 kernel; You probably won't. 2.6.18_164.11.1.0.1.el5 looks like an OEL5 kernel, not a RHEL5 kernel. I'd imagine you are actually using RHEL5 and you grabbed the OEL5 packages from the download site. > the closest > one is kernel-2.6.18-164.11.1.el5.x86_64.rpm. Which you can see above, I supported by our 1.8.3 packages. > I have also tried to build the client rpm from source but in the > /usr/src/redhat/RPMS/x86_64/ directory i can only find the server-side > rpms (lustre, lustre-debuginfo, lustre-modules, lustre-source, lustre > tests): Those are in fact client packages, despite the lack of "client" in their name. This is a defect in our RPM packaging which I hope will be fixed by the landing of some patches I am working on in another bug. It's possible that I have not fixed that one though. Please feel free to file a bug in any case. > cd /usr/src/lustre-1.8.3 > ./configure --with-linux=/usr/src/kernels/2.6.18-194.8.1.el5-x86_64 > make rpms Well, you only want to do this if your target kernel will be 2.6.18-194.8.1.el5. But if your target kernel is in fact 2.6.18-164.el5 as you wrote above, you want to install the kernel-devel for 2.6.18-164.el5 and point to /usr/src/kernels/2.6.18-164.el5. b. [1] If you are familiar with how weak modules works, you might be able to get the modules from the lustre client modules package for 2.6.18_164.11.1.el5 to work with 2.6.18-164.el5. Our packages don't yet support weak modules, formally, but if you know how they work, you can do it manually. A future release will support weak modules, but that will depend on Redhat also adding more symbols to their kABI whitelist.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
