Dmesg and syslog are clean and has no entries about lustre client. And on the server side, there is no entry on the client side connection attempt either. Tcpdump shows no trace of incoming client connection request. I think it is the syntax of the MGSNID of the mount.lustre is not interpreted by the client correctly or I am missing some configuration on the client side to turn the "192.168.0.2@tcp0" to a valid NID, ie lustre device for the client to make an outwards connection request to the server.
Thanks, Yang -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Brian J. Murrell Sent: Tuesday, February 22, 2011 11:04 AM To: [email protected] Subject: Re: [Lustre-discuss] Help! Newbie trying to set up Lustre network On 11-02-22 02:00 PM, Xiang, Yang wrote: > It fails and complains about: > > mount.lustre: mount 192.168.0.2@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 The first thing to check in such situations is the client's syslog and/or dmesg. b. -- Brian J. Murrell Senior Software Engineer Whamcloud, Inc. _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
