Managing Serviceguard NFS for Linux, July 2007

Installing and Configuring Serviceguard NFS for Linux
Configuring a Serviceguard NFS Package
Chapter 236
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
NOTE The argument to be passed to the HA_APP_SCRIPT for lock migration
should contain the same name or IP address used by the clients
while mounting the exported file system.
Example: If client mounts the NFS file system using the package
name, specify the same in customer_defined_run_cmds as shown
below:
function customer_defined_run_cmds
{
$HA_APP_SCRIPT lock_migration:<package name>