Kushi2

82 Posts

3473

June 26th, 2009 18:00

Unable to NFS mount on to Linux server.

A file system has been created and exported to one of our Linux server. Our systems admin tried mounting it as NFS on to the server, but he's unable to access it and mount it. And some times the mount cmd hanged.

We provided the NAS network interface which is in the same subnet as the server is in. No network issues and no firewall issues.

Are we missing something that needs to be considered while exporting to linux servers?

Please let me know how can i proceed on this.

Responses(11)

dynamox

2 Intern

•

20.4K Posts

0

June 26th, 2009 22:00

try "showmount -e

Kushi2

82 Posts

0

June 27th, 2009 01:00

Yes, we tried that command but the NFS export didn't show up.
What is causing this? please help me resolving the issue.

dynamox

2 Intern

•

20.4K Posts

0

June 27th, 2009 05:00

can you run this from your linux server "rpcinfo -p | grep nfs". What does it come back with ?

R

Rainer_EMC

2 Intern

•

8.6K Posts

0

June 29th, 2009 05:00

Is that Linux client able to NFS mount from another server, like another Linux box ?

Kushi2

82 Posts

0

July 9th, 2009 14:00

We tried mounting it on to another Linux box and it worked. Our systems admin was able to mount it.

But its not working on the one where we actually wanted to mount it. When we did show mount on that box, celerraa is not at all responding.

Looks like celerra is not talking to the Linux box.

BillStein-Dell

Moderator

•

285 Posts

0

July 9th, 2009 14:00

Since you are able to mount on another Linux box, this tends to eliminate the Celerra as the suspect. Do you have any mount permissions on this export (i.e. access=, rw=, or root=)? If not, I'd be looking at a routing or VLAN issue.

Thanks
Bill

Kushi2

82 Posts

0

July 9th, 2009 15:00

Also when we come to routing,

The network interface on NAS, using which sys admin tried to mount, is in same segment as of Linux box (may be both of them are configured for same VLAN, am not sure about this --> will get back to you on this once i verify with our network team). server is able to ping celerra IP and Celerra is able to ping server.

nandas

1.5K Posts

0

July 9th, 2009 15:00

Is this server dual homed? I mean to say does it have more than IP addresses? It seems to me that it has more than one IP address and it is picking up the incorrect IP address while connecting to the Celerra through NFS.

Kushi2

82 Posts

0

July 9th, 2009 15:00

We have exported the NFS mount to the Linux server with Root access, Read & write access and IP of server is entered in access hosts feild also

R

Rainer_EMC

2 Intern

•

8.6K Posts

0

July 10th, 2009 05:00

In cases like this its very, very rarely the Celerra at fault

I would start with creating an export for all hosts or the whole subnet. If that works you can narrow it down using specific IP adresses or host names.

Also see if that Linux client is able to mount from a different NFS server to rule out its a problem with the client

mikesk813

21 Posts

0

August 28th, 2009 17:00

I had the same issue and I fixed it by issuing the following commands on my Linux clients:
#chkconfig portmap on
#service portmap start

View All

No Events found!