[Lustre-discuss] Modprobe lustre fails

mitcheloc mitcheloc at gmail.com
Mon Mar 10 11:32:22 PDT 2008


Isaac,

I checked my ethernet card and it didn't look like Quadrics hardware.

 [root at catapult ~]# lspci | grep Ethernet
00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network
Connection (rev 02)

So I removed the parameter, rebooted and it worked like a charm! I wonder
how that setting got into my modules.conf file. I checked on another CentOS
system I set up and it is not there. It was probably inserted by some other
DFS I was trying out.

After changing modules.conf and rebooting:

[root at catapult ~]# modprobe lustre
[root at catapult ~]# dmesg
Lustre: OBD class driver, info at clusterfs.com
        Lustre Version: 1.6.4.3
        Build Version:
1.6.4.3-19691231160000-PRISTINE-.usr.src.linux-2.6.18-53.1.14.el5.lustre
Lustre: Added LNI 192.168.0.3 at tcp [8/256]
Lustre: Accept secure, port 988
Lustre: Lustre Client File System; info at clusterfs.com

Thanks & hopefully I don't run into any other issues.

Cheers,
Mitchel

On Mon, Mar 10, 2008 at 12:48 PM, Isaac Huang <He.Huang at sun.com> wrote:

> On Mon, Mar 10, 2008 at 11:38:33AM -0500, mitcheloc wrote:
> >    From modprobe.conf:
> >
> >    options lnet networks=tcp0,elan0
>
> If you don't have Quadrics Elan hardware, you can change it to:
> options lnet networks=tcp0
>
> Otherwise,
>
> >    Where should kqswlnd.ko be coming from?
>
> you need to compile lustre with proper QsNet support.
>
> Isaac
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20080310/0d7ba230/attachment.htm>


More information about the lustre-discuss mailing list