[Lustre-discuss] Issue regarding lustre client mountpoint

linux freaker linuxfreaker at gmail.com
Sat May 4 04:27:40 PDT 2013


Hi Lee,

I have one lustreclient1 working fine. I followed it this way:

# lustre_rmmod

#modprobe lustre
#mount -t lustre 192.168.1.1 at o2ib0:/lustre /mnt/lustre

and it worked fine.

But when I am trying the same stuff on another machine, it threw the error:

 but another having some issue.

# lustre_rmmod
Modules still loaded:
lnet/klnds/socklnd/ksocklnd.o lnet/lnet/lnet.o libcfs/libcfs/libcfs.o

# modprobe lustre
# modprobe lnet
]# 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
]# mount -t lustre 192.168.1.1 at o2ib0
<https://lists.01.org/mailman/listinfo/hpdd-discuss>:/lustre
/mnt/lustre
mount.lustre: mount 192.168.1.1 at 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)



On Sat, May 4, 2013 at 1:02 PM, Lee, Brett <brett.lee at intel.com> wrote:

>  Looks like you are going from an Ethernet client to Lustre servers on an
> IB network. Have you configured LNet routing between these networks?****
>
> ** **
>
> Before trying to mount, ensure that the client can reach the MGS using:***
> *
>
> ** **
>
> [lustreclient1]# lctl ping 192.168.1.1 at o2ib0****
>
> ** **
>
> --****
>
> Brett Lee****
>
> Sr. Systems Engineer****
>
> Intel High Performance Data Division****
>
> ** **
>
> *From:* lustre-discuss-bounces at lists.lustre.org [mailto:
> lustre-discuss-bounces at lists.lustre.org] *On Behalf Of *linux freaker
> *Sent:* Friday, May 03, 2013 11:25 PM
> *To:* lustre-discuss
> *Subject:* [Lustre-discuss] Issue regarding lustre client mountpoint****
>
> ** **
>
> 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 at o2ib****
>
> ** **
>
> OSS1 and OSS2:****
>
> ** **
>
> # lctl list_nids****
>
> 192.168.1.2 at o2ib****
>
> ** **
>
>  cat /proc/fs/lustre/devices****
>
>   0 UP mgc MGC192.168.1.1 at 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 at lustreclient1 ~]# mount -t lustre 192.168.1.1 at o2ib:/lustre /mnt/lustre****
>
> mount.lustre: mount 192.168.1.1 at 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 at 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 at lustreclient1 ~]# ^C****
>
> [root at lustreclient1 ~]#****
>
> ** **
>
> Why client is not mounting. My MGS is working fine.****
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20130504/18b28fdd/attachment.htm>


More information about the lustre-discuss mailing list