Unix and Linux network configuration. Multiple network interfaces. Bridged NICs. High-availability network configurations.


Reviews of latest Unix and Linux software. Helpful tips for application support admins. Automating application support.


Disk partitioning, filesystems, directories, and files. Volume management, logical volumes, HA filesystems. Backups and disaster recovery.


Distributed server monitoring. Server performance and capacity planning. Monitoring applications, network status and user activity.

Commands & Shells

Cool Unix shell commands and options. Command-line tools and application. Things every Unix sysadmin needs to know.

Home » Networking

Fixing the mount.nfs: rpc.statd is not running Error

Submitted by on October 22, 2012 – 4:11 pm

The rpc.statd service is used by NFS client to help it recover from loss of connectivity to the NFS server. When rpc.statd is not running, NFS is not able to handle remote file locking. You would also be unable to mount an NFS without specifying the “nolock” option. The common error you would get will look something like this:

[root@client /]# mount server:/share /share
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

The problem may be that rpc.statd service is not enabled on start-up or that it started but died thereafter. Here are a few common steps to troubleshoot the problem:

1. Make certain you have nfs-util package installed

rpm -qa | grep nfs-utils

The output should look something like this:

2. See if statd daemon is running:
ps -ef | grep -i [s]tatd

On a healthy NFS client, the output would look similar to this:
rpcuser   1724     1  0 Oct05 ?        00:00:00 rpc.statd

If you don’t see statd running, you would need to restart three service: rpcbind, nfs and nfslock. Here’s how you would do this on a Red Hat system:
for i in rpcbind nfs nfslock
     /etc/init.d/$i restart

Try mounting the filesystem again. If things work fine, make sure nfslock is enabled on start-up:
/sbin/chkconfig nfslock on

If you were able to mount NFS from this client before and now it’s not working, you may try rebooting the client.

Print Friendly, PDF & Email

Leave a Reply