[Lustre-discuss] Help! Newbie trying to set up Lustre network

[Bob Ball]

Quite often, sunrpc takes the port needed by Lustre, before Lustre can 
get to it.  That results in the messages below.   No recourse but to 
reboot.  Put the mount in your /etc/fstab as the simplest approach.  
This may not be the ONLY reason why this happens, but it is the one that 
has most often bitten me.

10.10.1.140 at tcp0:/myLustre /lustre/myLustre lustre _netdev,localflock 0 0

bob

On 2/22/2011 2:00 PM, Xiang, Yang wrote:
>
> I am completely new to this and have a simple question.
>
> The lustre version I am using is 1.8.5 on  SLES10 x86_64 machines.
>
> I've set up a server with combined MGS and OST on "eth2" with an lnet 
> entry in modprobe.conf:
>
> options lnet networks=tcp0(eth2)
>
> and the ip address for eth2 is: 192.168.0.2
>
> when I do "lctl list_nids" on the server, it correctly responds by:
>
> 192.168.0.2 at tcp
>
> And on a client, I only installed lustre-client-modules-<ver> and 
> lustre-client-<ver> rpms. And I can ping the server.
>
> However, when I tried to mount the lustre on the client by doing:
>
> mount -t lustre 192.168.0.2 at tcp0:/temp /lustre
>
> It fails and complains about:
>
> mount.lustre: mount 192.168.0.2 at tcp0:/temp at /lustre failed: No such 
> device
>
> Are the lustre modules loaded?
>
> Check /etc/modprobe.conf and /proc/filesystems
>
> Note 'alias lustre llite' should be removed from modprobe.conf
>
> Any idea what's going on there?
>
> Please help. I am reading the LNET configuration chapter and could not 
> find anything relating to client side NID correlation.
>
> Thanks,
>
> Yang
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20110222/adc7b0ca/attachment.htm>