Managing Serviceguard NFS for Linux, March 2009

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 start and monitor rpc.quotad daemon, set QUOTA_MON to YES. For example:
QUOTA_MON=YES
If you do not want to start and monitor rpc.quotad daemon, set QUOTA_MON to NO. For
example:
QUOTA_MON=NO
Configuring Lock Migration Feature
The following steps need to be completed to use of the lock migration feature:
1. In the package configuration file, set the SERVICE_FAIL_FAST_ENABLED to “YES” for the
NFS monitoring service. Example:
SERVICE_NAME nfs1.monitor
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300
NOTE: In Red Hat, there are times when sending SIGKILL to the kernel ‘lockd’ thread
might not release all the file locks and cause the failure of the unmounting of filesystem. To
force unmount of the filesystem, the machine has to be rebooted. In such cases, it is
recommended to set SERVICE_FAIL_FAST_ENABLED to “YES” which reboots the machine
upon service failure.
In SLES, the SM directory does not consistently update with the client entries. This is due to
the client entry being made for the first time only after the system has booted. After a fail
back of the package, the NFS fails to create SM directory entries. After a fail back, if the client
attempts to reclaim his locks, fresh entries for the clients will not be made in the /var/lib/
nfs/sm directory of the server. For SLES, it is mandatory to set
SERVICE_FAIL_FAST_ENABLED to “YES”, so the server reboots in order to have lock
migration feature work consistently.
If you halt the package manually on any node configured for an NFS package, you must
reboot the machine before the package is run again on the same node.
2. In the Package Control Script, edit the customer_defined_run_cmds function to execute
the toolkit.sh script for file lock migration. In the example below, the following line was
added, $HA_APP_SCRIPT lock_migration:<Package IP>.
NOTE: HA_APP_SCRIPT is initialized to the toolkit.sh path in the package control
script.
Example:
function customer_defined_run_cmds
{
$HA_APP_SCRIPT lock_migration:${IP[0]}
test_return 51
}
Copying the Template Files 25