From e3167df6ce1422c320adfa0496f66701f88555a5 Mon Sep 17 00:00:00 2001 From: Martin Schwenke Date: Tue, 14 Feb 2017 09:04:41 +1100 Subject: [PATCH] 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 Reviewed-by: Amitay Isaacs Autobuild-User(master): Martin Schwenke Autobuild-Date(master): Thu Feb 16 09:21:03 CET 2017 on sn-devel-144 (cherry picked from commit 5e7ae1b1e2fa8137aaa6a2a2f446156ae61f4c84) --- ctdb/config/statd-callout | 1 + 1 file changed, 1 insertion(+) 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 -- 2.11.0