[Lustre-discuss] Lustre 184.108.40.206 on X4200 and STK 6140 Issues
adilger at sun.com
Tue Oct 7 01:48:39 PDT 2008
On Oct 06, 2008 10:24 -0400, Ms. Megan Larko wrote:
> The order I used which generated no "unknown symbol" errors for
> installation of lustre 220.127.116.11 was this:
> 1) kernel-lustre-smp-2.6.18-53.1.14.el5_lustre.18.104.22.168.x86_64.rpm
> If using infiniband (IB) this is next:
> 2) kernel-ib-1.3-2.6.18_53.1.14.el5_lustre.22.214.171.124smp.x86_64.rpm
> 3) lustre-ldiskfs-3.0.4-2.6.18_53.1.14.el5_lustre.126.96.36.199smp.x86_64.rpm
> 4) lustre-modules-188.8.131.52-2.6.18_53.1.14.el5_lustre.184.108.40.206smp.x86_64.rpm
> 5) lustre-220.127.116.11-2.6.18_53.1.14.el5_lustre.18.104.22.168smp.x86_64.rpm
That is good to know for the documentation. However, I suspect if all
of these packages are installed at the same time there would also not
be any symbol warnings.
> If a module installation does have many "unknown symbol" references,
> then find the rpm which will satisfy those references and install that
> module. To actually have them satisfied one must return to the
> package that had complained about the "unknown symbol" and having
> already installed the package to satisfy those symbols then "rpm
> --force -ivh" to force a retry of the package with the issues.
That isn't quite correct. The missing module symbols are the output
of "depmod -ae" that is run in the RPM post-install after kernel modules
are installed. Even if there are such warnings, if the modules are
later installed and "depmod -ae" is run again it should report no
warnings, regardless of what order the modules were installed. That
means - no need to reinstall the RPMs or to install them in a particular
order, though of course avoid the warnings is always nicer.
You can always run "depmod -ae" by hand to re-verify the modules of
the currently installed kernels.
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
More information about the lustre-discuss