diff options
author | Rong Zeng <rongzeng@us.ibm.com> | 2014-06-01 13:04:48 -0400 |
---|---|---|
committer | Steve Dickson <steved@redhat.com> | 2014-06-01 13:10:02 -0400 |
commit | a126e718ab931963ca877fd11203f873fd50811f (patch) | |
tree | bc445e1cdf15217adfce6b0257720fc4850e162a /utils/statd/statd.man | |
parent | 548bbdc49b1f5dfbe7ba75d20c5791652dfeb125 (diff) | |
download | nfs-utils-a126e718ab931963ca877fd11203f873fd50811f.tar.gz nfs-utils-a126e718ab931963ca877fd11203f873fd50811f.tar.xz nfs-utils-a126e718ab931963ca877fd11203f873fd50811f.zip |
statd: Adding callback on sm_notify
This patch adds a callback for incoming sm_notify to better handle
stale lock issue in client crash recovery in HA-NFS environment
1. "sm-notify" - callout name
2. monitored client name as in the SM_NOTIFY request
3. IP of the sender of the SM_NOITFY request.
4. state value in the SM_NOTIFY request
This new interface can be used by different HA-NFS product
in its specific configuration and environment to
recover from the client crash and stale lock scenarios.
Signed-off-by: Rong Zeng <rongzeng@us.ibm.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/statd/statd.man')
-rw-r--r-- | utils/statd/statd.man | 20 |
1 files changed, 16 insertions, 4 deletions
diff --git a/utils/statd/statd.man b/utils/statd/statd.man index 896c2f8..1e5520c 100644 --- a/utils/statd/statd.man +++ b/utils/statd/statd.man @@ -346,7 +346,8 @@ points due to inactivity. .SS High-availability callouts .B rpc.statd can exec a special callout program during processing of -successful SM_MON, SM_UNMON, and SM_UNMON_ALL requests. +successful SM_MON, SM_UNMON, and SM_UNMON_ALL requests, +or when it receives SM_NOTIFY. Such a program may be used in High Availability NFS (HA-NFS) environments to track lock state that may need to be migrated after a system reboot. @@ -357,15 +358,26 @@ option. The program is run with 3 arguments: The first is either .B add-client -or .B del-client +or +.B sm-notify depending on the reason for the callout. The second is the .I mon_name of the monitored peer. The third is the -.I caller_name -of the requesting lock manager. +.I caller_name +of the requesting lock manager for +.B add-client +or +.B del-client +, otherwise it is +.I IP_address +of the caller sending SM_NOTIFY. +The forth is the +.I state_value +in the SM_NOTIFY request. + .SS IPv6 and TI-RPC support TI-RPC is a pre-requisite for supporting NFS on IPv6. If TI-RPC support is built into |