diff options
| author | Martin Schwenke <martin@meltin.net> | 2017-02-14 09:04:41 +1100 |
|---|---|---|
| committer | Martin Schwenke <martins@samba.org> | 2017-02-16 09:21:03 +0100 |
| commit | 5e7ae1b1e2fa8137aaa6a2a2f446156ae61f4c84 (patch) | |
| tree | 8cbe2ee728188387fe78d2a4afb85c23dd0d4b21 /ctdb/config | |
| parent | 024a2c20d2bcdbcc43d16d492c7cd2d09b93c8f0 (diff) | |
| download | samba-5e7ae1b1e2fa8137aaa6a2a2f446156ae61f4c84.tar.gz | |
ctdb-scripts: Initialise CTDB_NFS_CALLOUT in statd-callout
Some configurations may set CTDB_NFS_CALLOUT to the empty string.
They may do this if they allow a choice of NFS implementations. In
this case the default call-out for Linux kernel NFS should be used.
However, statd-callout does not call nfs_callout_init() to set the
default. Therefore, statd-callout is unable to restart the lock
manager, so the grace period is never entered.
statd-callout must call nfs_callout_init() before trying to restart
the lock manager.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=12589
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Autobuild-User(master): Martin Schwenke <martins@samba.org>
Autobuild-Date(master): Thu Feb 16 09:21:03 CET 2017 on sn-devel-144
Diffstat (limited to 'ctdb/config')
| -rwxr-xr-x | ctdb/config/statd-callout | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/ctdb/config/statd-callout b/ctdb/config/statd-callout index 3f2dd39f68f..38f847b1d9b 100755 --- a/ctdb/config/statd-callout +++ b/ctdb/config/statd-callout @@ -128,6 +128,7 @@ case "$1" in # where the lock manager will respond "strangely" immediately # after restarting it, which causes clients to fail to reclaim # their locks. + nfs_callout_init "$CTDB_NFS_CALLOUT" "stop" "nlockmgr" >/dev/null 2>&1 sleep 2 "$CTDB_NFS_CALLOUT" "start" "nlockmgr" >/dev/null 2>&1 |