topic Re: NFS Mount Problem in Operating System - HP-UX

NFS Mount Problem

Nagu SR — Tue, 10 Mar 2009 02:33:15 GMT

Hi,

Both client and server--HP-UX 11.31-NFS 3

We had hard mounted one filesystem which is not accessible now. any command related to NFS is not working. `bdf` says /FILESYS is not responding. We had tried options (Only in Client) like umount (Doesnt work) restarted NFS services like `nfs.server`; autofs; nfs.client; lockmgr; nfs.core but still problem persists.
I had been to somany NFS threads in ITRC, but most of the sites had given me hope that the NFS issues are addressed in 11.31. If so, is there any way other than reboot??

NFS Patch-- B.11.31;
And we are able to mount the NFS server's exported filesys in other clients.(same OS-NFS patch level) Problem is only in one client.

Can someone help me please???

Re: NFS Mount Problem

sujit kumar singh — Tue, 10 Mar 2009 04:10:06 GMT

Hi
I assume that the server 11.31 acting as the NFS server has only one client.
apart from trying the restart of the NFS services on the client, can you try unexporting the Filesystem and if not much impact on the server restarting the NFS services and reexporting them then mount on the client?
regards
sujit

Re: NFS Mount Problem

Sameer Kelkar — Tue, 10 Mar 2009 04:18:55 GMT

#showmount -e

is this command showing proper output ?

Re: NFS Mount Problem

Avinash20 — Tue, 10 Mar 2009 04:21:44 GMT

So it only the NFS client which is having the issue

Could you post the output of below command from NFS client.

# rpcinfo -p
# rpcinfo -p

Re: NFS Mount Problem

Nagu SR — Tue, 10 Mar 2009 04:53:25 GMT

Hi,

I cant do the restart of NFS service in NFS server as it would have major Prod Impact.

The Output of the command
`rpcinfo -p servername`

program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100024 1 udp 49207 status
100021 1 udp 4045 nlockmgr
100021 2 udp 4045 nlockmgr
100024 1 tcp 49152 status
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 2 tcp 4045 nlockmgr
100133 1 udp 49207
100021 3 tcp 4045 nlockmgr
100133 1 tcp 49152
100021 4 tcp 4045 nlockmgr
1073741824 1 tcp 49153
100005 1 udp 49627 mountd
100005 1 tcp 49274 mountd
100005 2 udp 49627 mountd
100005 2 tcp 49274 mountd
100005 3 udp 49627 mountd
100005 3 tcp 49274 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 2 udp 2049
100227 3 udp 2049
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 2 tcp 2049
100227 3 tcp 2049

showmount -e servername

export list for servername:
/oradump (everyone)
/var/opt/ignite/clients (everyone)

I had problem in accessing /oradump. now when I tried mouonting other Filesys (/var/opt/ignite/clients) I'm not able to mount it as well. I even tried mounting different servers NFS volumes here but it failed. So problem is with only client

Thx

Regards
Nagu

Re: NFS Mount Problem

Nagu SR — Thu, 19 Mar 2009 05:48:25 GMT

Hi,

We had to reboot the NFS client to fix the issue.

However, we have updated NFS version to ONCplus version B.11.31.06 as suggested by HP.

Regards,
Nagu