Red Hat Bugzilla – Bug 832260
A Red Hat Storage server cannot mount an external kernel NFS volume without nolock option.
Last modified: 2014-03-30 21:29:00 EDT
Description of problem:
When a Red Hat Storage server mounts a kernel NFS server without nolock option, an error displays. So in the case it always needs the option and NLM will be unavailable.
Version-Release number of selected component (if applicable):
Red Hat Storage 2.0 beta 2
mount -t nfs <IP ADDR>:<PATH/TO/EXPORT> <PATH/TO/MOUNT>
No error case:
mount -t nfs -o nolock <IP ADDR>:<PATH/TO/EXPORT> <PATH/TO/MOUNT>
Steps to Reproduce:
mount.nfs: access denied by server while mounting <IP ADDR>:<PATH/TO/EXPORT>
I assume that GlusterFS holds nlockmgr RPC and it conflicts with mountd when the RHS server behaves as a kernel NFS client.
Your reason under "Additional info" is close to the answer. What happens is - glusterfs-nfs starts runs nlm server and registers with portmapper for NLMv4, nfs client also starts NLM server (i.e lockd in the kernel) which fails resulting in this issue. Documentation team will document this behaviour.
Thank you for the information. I understand the mechanism and that it should be documented.
So, in a view of bugzilla, I would like to close this bug.