Re: [HPDD-discuss] Issue setting up Lustre Client

I tried on another lustreclient but could nt get it working.. [root@lustreclient2 ~]# lustre_rmmod Modules still loaded: lnet/klnds/socklnd/ksocklnd.o lnet/lnet/lnet.o libcfs/libcfs/libcfs.o [root@lustreclient2 ~]# [root@lustreclient2 ~]# modprobe lustre [root@lustreclient2 ~]# modprobe lnet [root@lustreclient2 ~]# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.233 ms ^C --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 982ms rtt min/avg/max/mdev = 0.233/0.233/0.233/0.000 ms [root@lustreclient2 ~]# mount -t lustre 192.168.1.1@o2ib0:/lustre /mnt/lustre mount.lustre: mount 192.168.1.1@o2ib0:/lustre at /mnt/lustre failed: No such file or directory Is the MGS specification correct? Is the filesystem name correct? If upgrading, is the copied client log valid? (see upgrade docs) [root@lustreclient2 ~]# ^C [root@lustreclient2 ~]# Any idea ? On Sat, May 4, 2013 at 9:25 AM, linux freaker <linuxfreaker(a)gmail.com&gt;wrote: > Wow !!! Great. > > lctl list_nids > 192.168.1.4@o2ib > > It worked !! I am able to mount it. > > > > On Sat, May 4, 2013 at 9:21 AM, Diep, Minh <minh.diep(a)intel.com&gt; wrote: > >> #lctl list_nids >> 10.94.214.188@tcp >> >> >> If this is on the client, then it's wrong network. Do a lustre_rmmod to unload module and load lent with correct x.x.x.x@o2ib >> >> >> Thanks >> >> -Minh >> >> >> From: linux freaker <linuxfreaker(a)gmail.com&gt; >> Date: Friday, May 3, 2013 8:24 PM >> To: &quot;hpdd-discuss(a)lists.01.org&quot; <hpdd-discuss(a)lists.01.org&gt; >> Subject: [HPDD-discuss] Issue setting up Lustre Client >> >> My MDS and OSS configuration look like: >> >> MDS: >> >> #mount >> /dev/mapper/vg00-mdt on /mnt/mdt type lustre (rw) >> >> lctl list_nids >> 192.168.1.1@o2ib >> >> OSS1 and OSS2: >> >> # lctl list_nids >> 192.168.1.2@o2ib >> >> cat /proc/fs/lustre/devices >> 0 UP mgc MGC192.168.1.1@o2ib fe161cab-092e-5a7b-0ac1-6081653d099e 5 >> 1 UP ost OSS OSS_uuid 3 >> 2 UP obdfilter lustre-OST0006 lustre-OST0006_UUID 5 >> 3 UP obdfilter lustre-OST0007 lustre-OST0007_UUID 5 >> 4 UP obdfilter lustre-OST0008 lustre-OST0008_UUID 5 >> 5 UP obdfilter lustre-OST0009 lustre-OST0009_UUID 5 >> 6 UP obdfilter lustre-OST000a lustre-OST000a_UUID 5 >> 7 UP obdfilter lustre-OST000b lustre-OST000b_UUID 5 >> >> >> LustreClient: >> >> [root@lustreclient1 ~]# mount -t lustre 192.168.1.1@o2ib:/lustre /mnt/lustre >> mount.lustre: mount 192.168.1.1@o2ib0:/lustre at /mnt/lustre failed: No such file or directory >> Is the MGS specification correct? >> Is the filesystem name correct? >> If upgrading, is the copied client log valid? (see upgrade docs) >> >> #lctl list_nids >> 10.94.214.188@tcp >> >> Please note that earlier I had 10.94.214.188 as MDS which is still being displayed. I am not sure if lctl list nids need to run on client. >> >> >> [root@lustreclient1 ~]# ^C >> [root@lustreclient1 ~]# >> >> Why client is not mounting. My MGS is working fine. >> >> >