statd Daemon

Note:

NFS Version 4 does not use this daemon.

The statd daemon works with lockd to provide crash and recovery functions for the lock manager. The statd daemon tracks the clients that hold locks on an NFS server. If a server crashes, on rebooting, statd on the server contacts statd on the client. The client statd can then attempt to reclaim any locks on the server. The client statd also informs the server statd when a client has crashed so that the client's locks on the server can be cleared. This daemon has no options. For more information, see the statd(8) man page.

The statd daemon must be able to process numerous concurrent requests quickly. An insufficient number of available threads might result in incoming requests from unregistered clients stalling and preventing statd from processing further requests from such clients.

You can use the sharectl command to update the statd_servers SMF property value, which specifies the number of concurrent statd threads that can run on a server. The statd daemon reads the statd_servers property value at startup. The daemon uses the specified property value or the default value of 1024. A valid value is an integer of at least 1024.

When the statd daemon is unable to process more incoming requests due to the threads being exhausted, test the configuration by running a command such as rpcinfo -T tcp localhost status. If the command issues the Program program-name not available error, use the sharectl command to set the statd_servers property value to a larger number of threads. See the sharectl(8) man page.

Use the statd_servers property to temporarily work around problems where statd is unable to process incoming requests.

Note that when you specify a new statd_servers property value, syslog issues a message that shows the updated number of statd threads.