Overview of MC/ServiceGuard NFS
How the Control and Monitor Scripts Work
How the Control and Monitor Scripts Work
As with all ServiceGuard packages, the control script starts and stops the NFS package and determines how the package operates when it is available on a particular node. The 11i v1 and 11i v2 control script (hanfs.sh) contains three sets of code that operate depending on the parameter - start, stop, or file_lock_migration - with which you call the script. On 11.0, there are two sets of code that you can call with the start or stop parameter.
Starting the NFS Services
When called with the start parameter, the control script does the following:
•Activates the volume group or volume groups associated with the package.
•Mounts each file system associated with the package.
•Initiates the NFS monitor script to check periodically on the health of NFS services, if you have configured your NFS package to use the monitor script.
•Exports each file system associated with the package so that it can later be
•Assigns a package IP address to the LAN card on the current node.
After this sequence, the NFS server is active, and clients can
Starting File Lock Migration
If you call the control script with the file_lock_migration parameter after enabling the File Lock Migration feature, the control script does the following:
•Populates the /var/statmon/sm directory with the Status Monitor entries from the configured holding directory of the package, and subsequently removes the entries from the holding directory.
•Kills any running copy of the NFS File Lock Recovery synchronization script.
Chapter 1 | 19 |