Deferred attach : at early startup, defer any db attach calls until we are out of...

[sahlberg/ctdb.git] / web / nfs.html

diff --git a/web/nfs.html b/web/nfs.html
index 6bec33bc648b8f00f48c3a86117959324e8df2cb..a4a6fb5e0420e1e4c653052679d569c11816c31b 100644 (file)
--- a/web/nfs.html
+++ b/web/nfs.html
@@ -14,13 +14,6 @@ NFS for CTDB clustering</a> at samba.org for additional information.
 Configure CTDB as above and set it up to use public ipaddresses.<br>
 Verify that the CTDB cluster works.
 
-<h2>sm-notify</h2>
-
-Make sure you have the sm-notify tool installed in /usr/sbin.<br>
-You should find that tool in the nfs-util package for your operating system.<br><br>
-This tool is required so that CTDB will be able to successfully trigger lock recovery after an ip address failover/failback.<br><br>
-This tool must be installed as /usr/sbin/sm-notify on all nodes in the cluster.
-
 <h2>/etc/exports</h2>
 
 Export the same directory from all nodes.<br>
@@ -46,28 +39,35 @@ which causes problems on some clients.<br>
 
 This file should look something like :
 <pre>
-  CTDB_MANAGES_NFS=yes
+  NFS_HOSTNAME=ctdb
+  STATD_PORT=595
+  STATD_OUTGOING_PORT=596
+  MOUNTD_PORT=597
+  RQUOTAD_PORT=598
   LOCKD_TCPPORT=599
   LOCKD_UDPPORT=599
-  STATD_SHARED_DIRECTORY=/gpfs0/nfs-state
-  STATD_HOSTNAME="ctdb -P $STATD_SHARED_DIRECTORY/192.168.1.1 -H /etc/ctdb/statd-callout -p 97"
-</pre>
+  STATD_HOSTNAME="$NFS_HOSTNAME -H /etc/ctdb/statd-callout -p 97"
+  RPCNFSDARGS="-N 4"
 
-The CTDB_MANAGES_NFS line tells the events scripts that CTDB is to manage startup and shutdown of the NFS and NFSLOCK services.<br>
-
-With this set to yes, CTDB will start/stop/restart these services as required.<br><br>
+</pre>
 
 You need to make sure that the lock manager runs on the same port on all nodes in the cluster since some clients will have "issues" and take very long to recover if the port suddenly changes.<br>
 599 above is only an example. You can run the lock manager on any available port as long as you use the same port on all nodes.<br><br>
 
-STATD_SHARED_DIRECTORY is the shared directory where statd and the statd-callout script expects that the state variables and lists of clients to notify are found.<br>
+NFS_HOSTNAME is the dns name for the ctdb cluster and which is used when clients map nfs shares. This name must be in DNS and resolve back into the public ip addresses of the cluster.<br>
+Always use the same name here as you use for the samba hostname.
+
+RPCNFSDARGS is used to disable support for NFSv4 which is not yet supported by CTDB.
 
-This directory must be stored on the shared cluster filesystem so that all nodes can access the same data.<br><br>
+<h2>/etc/sysconfig/ctdb</h2>
+Add the following line to /etc/sysconfig/ctdb :
 
-Don't forget to create this directory:
 <pre>
-  mkdir /gpfs0/nfs-state
+  CTDB_MANAGES_NFS=yes
 </pre>
+The CTDB_MANAGES_NFS line tells the events scripts that CTDB is to manage startup and shutdown of the NFS and NFSLOCK services.<br>
+
+With this set to yes, CTDB will start/stop/restart these services as required.<br><br>
 
 
 <h2>chkconfig</h2>
@@ -81,7 +81,7 @@ Since CTDB will manage and start/stop/restart the nfs and the nfslock services,
 
 <h2>Event scripts</h2>
 
-CTDB clustering for NFS relies on two event scripts /etc/ctdb/events.d/nfs and /etc/ctdb/events.d/nfslock.<br>
+CTDB clustering for NFS relies on two event scripts /etc/ctdb/events.d/60.nfs and /etc/ctdb/events.d/61.nfstickle.<br>
 
 These two scripts are provided by the RPM package and there should not be any need to change them.