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

#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@gmail.com<mailto:linuxfreaker@gmail.com>> Date: Friday, May 3, 2013 8:24 PM To: "hpdd-discuss@lists.01.org<mailto:hpdd-discuss@lists.01.org>" <hpdd-discuss@lists.01.org<mailto:hpdd-discuss@lists.01.org>> 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.