This information describes how to contact a remote peer in case Rpc.statd records information about each monitored NFS peer on persistent storage. On Linux, the local lock manager contacts rpc.statd. ![]() The first file locking interaction between an NFS client and server causes the NFS lock managers on both peers to contact their local NSM service to store In turn passes the reboot notification back to the local NFS lock manager. When a remote reboots, that peer notifies the local rpc.statd, which ![]() ![]() Sm-notify command notifies the NSM service on monitored peers of the reboot. The local NFS lock manager alerts its local rpc.statd of each remote peer that should be monitored. Rpc.statd A daemon that listens for reboot notifications from other hosts, and manages the list of hosts to be notified when the local system reboots Sm-notify A helper program that notifies NFS peers after the local system reboots Separate user-space components constitute the NSM service: ![]() After a server reboots, a client must remind the server of file locks held byįor NFS version 2 and version 3, the Network Status Monitor protocol (or NSM for short) is used to notify NFS peers of reboots. After an NFS client reboots, an NFS server must releaseĪll file locks held by applications that were running on that client. Network file systems must also detect when lock state is lost because a remote host has rebooted. Lock state is thus lost when a host reboots. File locks are not part of persistent file system state.
0 Comments
Leave a Reply. |