Issues trying to mount a nfs4 share on sles 10 sp2

[MQAdm1n]

Attempts to do a mount -t nfs4 servername:/share /mnt hang.

Performing an strace of the mount shows that the mount command is attempting to find /sbin/mount.nfs4

The nfs server, client, and util packages are installled.

Did ps -ef | grep idmapd; ps -ef | grep gssd to check client side daemons and things look good. Not using gssd right now tho. Just want to get the thing to mount.

Firewalls are not running.

Doing a showmount -e servername reports the shares as being offered.

I can mount it using nfs v3 protocol.

Any ideas? It almost looks like I'm missing a package but have no idea what it might be.

[shtromm]

Perhaps a verbose output ("-v") would give a clue.

[MQAdm1n]

A -v to the mount command? Perhaps but the meat of the problem is shown in the strace output. The mount command continues to loop while attempting to stat /sbin/mount.nsf4. Similar files such as /sbin/mount.cifs exit and that was installed by a package. I considered cifs but it is not an option in this case. Cifs does not recognize chmod/chown or suid's which need to be done for the app that resides on the share.

[shtromm]

Do the Kernel-Server logs tell anything? May there is something helpful in /var/log/messages or /var/log/syslog ?

[MQAdm1n]

Unfortunately not. On either the client or server side, the /var/log/messages file is clean. Output from dmesg is inconclusive. The only entries are for the successful mounts using nfs v3. Wish i could stay at nfs 3 but WebSphere MQSeries v7.0.1x requires NFS 4 for better handling of stale mounts, performance, and kerberos security as applied to multi-instance queue manager fail-over strategies.

[whych]

Have you tried to mount it without the 'nfs4' entry?
(mount -t servername:/share /mnt)

nfs4 in sled 10 is a bit hit and miss and not really needed.

Also have you checked that nfs4 option is chcked in the sled 10 setup?

[MQAdm1n]

Hi whych.

Using the mount -t without specifying nfs4 defaults to protocol v3. Alternately you can specify the option explicitly using nfsvers=2 or nfsvers=3. SLES 11 is not an option at this time due to requirements for other applications. I checked the server side /etc/sysconfig/nfs and NFS4_SUPPORT is set to YES. NFS was restarted on the server to ensure it is active.

[HROAdmin26]

Google: "sles 10" "mount.nfs4" => Novell doc on using NFS4 on both server/client

If you don't have a mount.nfs4 script, then you don't have the client package installed. Use the zypper command to query for available packages.

[MQAdm1n]

Thank you for the link. I have been reviewing that and it is a great guide. I would agree on missing the client with but an rpm -qa shows the following:

sblim-cmpi-nfsv4-1.0.11-10.10
limal-nfs-server-1.1.72-0.3
yast2-nfs-server-2.13.10-0.3
limal-nfs-server-perl-1.1.72-0.3
nfsidmap-0.12-16.17
yast2-nfs-client-2.13.4-0.11
nfs-utils-1.0.7-36.29