Managing MC/ServiceGuard NFS for Linux, December 2001

Installing and Configuring MC/ServiceGuard NFS for Linux
Configuring a MC/ServiceGuard NFS Package
Chapter 2 29
Editing the NFS Control Script (hanfs.sh)
The following steps describe the required modifications to the NFS
Control Script.
1. Create a separate XFS[n] variable for each NFS directory to be
exported. Specify the directory name and any export options. For
example:
XFS[0]=”*:/ha_root”
XFS[1]=”*:/users/scaf”
XFS[2]=”-o ro *:/ha_data”
Do not configure these exported directories in the /etc/exports file.
When an NFS server boots up, it attempts to export all file systems
in its /etc/exports file. If those file systems are not currently
present on the NFS server node, the node cannot boot properly. This
happens if the server is an adoptive node for a file system, and the
file system is available on the server only after failover of the
primary node.
2. If you want to run the NFS monitor script:
• Set the NFS_SERVICE_NAME variable to the value of the
SERVICE_NAME variable in the package configuration file. Each
package must have a unique service name. For example:
NFS_SERVICE_NAME[0]=nfs1.monitor
• Set the NFS_SERVICE_CMD variable to the full path name of the
NFS monitor script. For example:
NFS_SERVICE_CMD[0]=/usr/local/cmcluster/pkg1/nfs.mon
The path name for the executable script does not have to be
unique to each package. Every package can use the same script.
Multiple instances of the monitor script can run on the same
node without any problems, and if a package fails over, only the
instance associated with that package is killed.
3. If you do not want to run the NFS monitor script:
Comment out the NFS_SERVICE_NAME and NFS_SERVICE_CMD
variables. For example:
# NFS_SERVICE_NAME[0]=nfs1.monitor
By default, the NFS_SERVICE_NAME and NFS_SERVICE_CMD variables
are commented out, and the NFS monitor script is not run.