Red Hat Bugzilla – Bug 799287
Support for Solaris NLM client
Last modified: 2015-08-10 03:44:57 EDT
Description of problem:
Solaris client is not able to use glusterfs NLM for locking
Solaris nfs client is mount like this:
mount -o proto=tcp,vers=3 nfs://HOSTNAME-OR-IPADDRESS:38467/VOLNAME MOUNTDIR
Because of this the NFS client does not do a portmap query of glusterfs NLM server and does not use its locking facility.
Looking at the wireshark dump of solaris nfs client mount from linux kernel nfs server, this is what it does:
1) query portmapper for UDP mountd
2) call MNT procedure on mountd to get root filehandle
3) when fcntl-lock is done, query portmap for TCP NLMv4
4) call NLM lock/unlock operations
But in case of glusterfs-nfs, solaris nfs client never does a portmap query for NLM server.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
To fix this we need to implement mountd on UDP so that solaris nfs client queries portmapper for NLM after query for MOUNT on UDP is successful.
Verified this, this feature is implemented. sub-directory mount does not work but there is a separate bug for it.