Difference between revisions of "nfs mount error - rpc.statd is not running"
From thelinuxwiki
(→solution) |
|||
| Line 6: | Line 6: | ||
mount.nfs: rpc.statd is not running but is required for remote locking. | 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: Either use '-o nolock' to keep locks local, or start statd. | ||
| + | |||
| + | O.S. = gentoo linux | ||
==versions== | ==versions== | ||
| Line 16: | Line 18: | ||
net-fs/nfs-utils Installed versions: 1.3.3 | net-fs/nfs-utils Installed versions: 1.3.3 | ||
| + | |||
| + | These are NFS version 4 compliant client/server packages | ||
==solution== | ==solution== | ||
Latest revision as of 20:15, 6 May 2016
Contents |
problem
NFS mount failing
Error message:
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.
O.S. = gentoo linux
versions
server
net-fs/nfs-utils Installed versions: 1.3.1-r5
client
net-fs/nfs-utils Installed versions: 1.3.3
These are NFS version 4 compliant client/server packages
solution
start nfsclient on the client..
- /etc/init.d/nfsclient start
then the nfs mount worked correctly
discussion
when I first saw the error messages, I check the NFS server and saw rpc.statd was not running
