[Lustre-discuss] Newbie - Unable to mount the OST on the Client

[Gupta, Amit]

Rick,

I am not seeing any messages on the MGS.. The messages that I see on the Client ( on which I am trying the mount operation) are

Jan  7 17:32:27 client kernel: LustreError: 156-2: The client profile 'client1-client' could not be read from the MGS.  Does that filesystem exist?
Jan  7 17:32:27 client kernel: LustreError: 11278:0:(lov_obd.c:951:lov_cleanup()) client1-clilov-ffff8810334fa000: lov tgt 0 not cleaned! deathrow=0, lovrc=1
Jan  7 17:32:27 client kernel: Lustre: Unmounted client1-client
Jan  7 17:32:27 client kernel: LustreError: 13411:0:(obd_mount.c:1342:lustre_fill_super()) Unable to mount  (-22)

Is there is a way to check if the Client is getting to the MGS to read the profile information.  That would atleast prove that the LNET configuration is good.

Thanks

-----Original Message-----
From: Mohr Jr, Richard Frank (Rick Mohr) [mailto:rmohr at utk.edu] 
Sent: Wednesday, January 07, 2015 12:38 PM
To: Gupta, Amit
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [Lustre-discuss] Newbie - Unable to mount the OST on the Client


On Jan 7, 2015, at 8:25 AM, "Gupta, Amit" <amit.gupta at optum.com> wrote:

> [root at Client ~]# mount -t lustre 10.177.33.10 at tcp:/client1 /mnt/lustre
> mount.lustre: mount 10.177.33.10 at tcp:/client1 at /mnt/lustre failed: 
> Invalid argument This may have multiple causes.
> Is 'client1' the correct filesystem name?
> Are the mount options correct?
> Check the syslog for more info

What do the syslog messages look like on the MGS server when this happens?

--
Rick Mohr
Senior HPC System Administrator
National Institute for Computational Sciences http://www.nics.tennessee.edu



This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.