From 3183ca1bdee9cb0af22c017e3c610add8ff2b405 Mon Sep 17 00:00:00 2001 From: Hendrik Visage Date: Fri, 19 May 2017 12:21:37 +0530 Subject: scripts/shared_storage : systemd helper scripts to mount shared storage post reboot Reported-by: Hendrik Visage Change-Id: Ibcff56b00f45c8af54c1ae04974267c2180f5f63 BUG: 1452527 Signed-off-by: Jiffin Tony Thottan Reviewed-on: https://review.gluster.org/17339 Smoke: Gluster Build System NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Niels de Vos Reviewed-by: Kaleb KEITHLEY --- extras/mount-shared-storage.sh | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100755 extras/mount-shared-storage.sh (limited to 'extras/mount-shared-storage.sh') diff --git a/extras/mount-shared-storage.sh b/extras/mount-shared-storage.sh new file mode 100755 index 00000000000..038a59aaabf --- /dev/null +++ b/extras/mount-shared-storage.sh @@ -0,0 +1,37 @@ +#!/bin/bash +#Post reboot there is a chance in which mounting of shared storage will fail +#This will impact starting of features like NFS-Ganesha. So this script will +#try to mount the shared storage if it fails +#TODO : Do it for other glusterfs clients in /etc/fstab + +ms="var-run-gluster-shared_storage.mount" +volume="gluster_shared_storage" +failed=$(systemctl --failed | grep -c $ms) +if [ $failed -eq 1 ] +then + if systemctl restart $ms + then + #Restart worked just wait for sometime to make it reflect + sleep 5 + else + #Restart failed, no point in further continuing + exit 1 + fi +fi + +# If we've reached this point, there wasn't a failed mountpoint +# BUT we need to check for whether this haven't been called before the attempts +# to the filesystem mounts, thus we need to check whether there is a glusterfs +# in fstab and aren't mountedmount + +#In the logs I've seen ~4-5secs between the initial mount/start and the unmount + +gfc=$(sed -e 's/#.$//'