Difference between revisions of "nfs mount error - rpc.statd is not running"
From thelinuxwiki
(Created page with "==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, o...") |
(→solution) |
||
| Line 19: | Line 19: | ||
==solution== | ==solution== | ||
| + | start nfsclient on the client.. | ||
| + | |||
| + | # /etc/init.d/nfsclient start | ||
| + | |||
| + | then the nfs mount worked correctly | ||
==discussion== | ==discussion== | ||
when I first saw the error messages, I check the NFS server and saw rpc.statd was not running | when I first saw the error messages, I check the NFS server and saw rpc.statd was not running | ||
Revision as of 20:14, 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.
versions
server
net-fs/nfs-utils Installed versions: 1.3.1-r5
client
net-fs/nfs-utils Installed versions: 1.3.3
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
