When I was using gluster-native NFS to export volume, I noticed that there is service 'nlockmgr' with tcp version4, but not with udp version4.
System: Ubuntu 12.04 with GlusterFS 3.5.7
The procedure to reproduce is as follow:
/* assuming glusterfs has been already installed */
step 1: # reboot /* waiting for the start of system */
step 2: # /etc/init.d/nfs-kernel-server stop
step 3: # /etc/init.d/idmapd stop
step 4: # rmmod nfsd
step 5: # rmmod lockd
step 6: # gluster volume start ... force
/* step 2 - step 6: avoid the confilct between nfs-kernel and glusterfs-native nfs */
The nfs.log is as follow:http://termbin.com/9oce
The result of "rpcinfo -p" is as follow: http://termbin.com/bcoa
The condition seems that the implementation of glusterfs doesn't support NLMv4 with UDPv4.
When using Black Disk Speed Test on MAC OS to do performance test at volume that is mounted through NFS from glusterfs's export, the program remained no reaction. It was realized that Some program such as Black Disk Speed Test on MAC OS requests nlm over UDPv4 after I used WireShark to analyze it's reason.
For comparison, the program is normal when doing performance test at volume which is mounted from nfs-kernel's export. So the reason is confirmed as that protocols are not the same: the program requests NLMv4 on UDP, but glusterfs only supports NLMv4 over TCP.
Then the question is that how to solve this problem.
In additon, I'm puzzled by this: why not support NLM with UDPv4? It seems simple to implement it now that NLM with TCPv4 is supported already.
I'm looking forward your reply, and any answer will be appreciated.
In addition, thanks for 'ndevos' on IRC for doing me a lot of favor.
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
