While mounting NFS file systems I've seen a rpc.statd error which prevents NFS file systems from being mounted.
When I try to mount the file system the following exact error is displayed:
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Now if we mount the file system using nolock option we will be able to mount the file system but it's not a recommended setting. Using nolock option disables file locking & I've seen it interfere with application functionality for applications using the NFS mount.
The fix for the error is to persistently start the rpcbind service.
The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine. NFS uses RPC for accessing data remotely. rpcbind uses port number 111.
When I try to mount the file system the following exact error is displayed:
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Now if we mount the file system using nolock option we will be able to mount the file system but it's not a recommended setting. Using nolock option disables file locking & I've seen it interfere with application functionality for applications using the NFS mount.
The fix for the error is to persistently start the rpcbind service.
The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine. NFS uses RPC for accessing data remotely. rpcbind uses port number 111.
No comments:
Post a Comment