Rpc.statd: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
=Prevent to Boot= | =Prevent to Boot= | ||
<pre> | |||
chkconfig --level 2345 nfslock off | chkconfig --level 2345 nfslock off | ||
</pre> | |||
=Handling NFS Locking in Absence of <tt>rpc.statd</tt>= | =Handling NFS Locking in Absence of <tt>rpc.statd</tt>= | ||
If we attempt to mount a NFS file on a host that does not run rpc.statd, we get this: | If we attempt to mount a NFS file on a host that does not run rpc.statd, we get this: | ||
<pre> | |||
[root@shrike rackstation]# mount -t nfs 192.168.1.4:/volume3/nopartnerwiki /rackstation/nopartnerwiki/ | [root@shrike rackstation]# mount -t nfs 192.168.1.4:/volume3/nopartnerwiki /rackstation/nopartnerwiki/ | ||
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. | ||
</pre> | |||
For front-end machines that are designed to exclusively access the remote storage, maintaining local locks might be acceptable. <font color=red>TODO: do more research on that, this is just intuition by now. What exactly does a NFS lock do?</font> | For front-end machines that are designed to exclusively access the remote storage, maintaining local locks might be acceptable. <font color=red>TODO: do more research on that, this is just intuition by now. What exactly does a NFS lock do?</font> | ||
| Line 26: | Line 25: | ||
In order to maintain local locks, mount like this: | In order to maintain local locks, mount like this: | ||
<pre> | |||
mount -t nfs -o nolock 192.168.1.4:/volume3/nopartnerwiki /rackstation/nopartnerwiki/ | mount -t nfs -o nolock 192.168.1.4:/volume3/nopartnerwiki /rackstation/nopartnerwiki/ | ||
</pre> | |||
Latest revision as of 06:52, 21 August 2016
Internal
Overview
A daemon that listens for reboot notifications from other hosts, and manages the list of hosts to be notified when the local system reboots. Used by NFS locking mechanism.
Prevent to Boot
chkconfig --level 2345 nfslock off
Handling NFS Locking in Absence of rpc.statd
If we attempt to mount a NFS file on a host that does not run rpc.statd, we get this:
[root@shrike rackstation]# mount -t nfs 192.168.1.4:/volume3/nopartnerwiki /rackstation/nopartnerwiki/ 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.
For front-end machines that are designed to exclusively access the remote storage, maintaining local locks might be acceptable. TODO: do more research on that, this is just intuition by now. What exactly does a NFS lock do?
In order to maintain local locks, mount like this:
mount -t nfs -o nolock 192.168.1.4:/volume3/nopartnerwiki /rackstation/nopartnerwiki/