From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/rgmanager/src/resources clusterfs.sh
Date: 13 Nov 2007 17:38:02 -0000 [thread overview]
Message-ID: <20071113173802.28111.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL5
Changes by: lhh at sourceware.org 2007-11-13 17:38:02
Modified files:
rgmanager/src/resources: clusterfs.sh
Log message:
Add self_fence support to RHEL5 branch for clusterfs
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/src/resources/clusterfs.sh.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.15.2.2&r2=1.15.2.3
--- cluster/rgmanager/src/resources/clusterfs.sh 2007/05/21 15:57:29 1.15.2.2
+++ cluster/rgmanager/src/resources/clusterfs.sh 2007/11/13 17:38:02 1.15.2.3
@@ -133,6 +133,18 @@
<content type="string"/>
</parameter>
+ <parameter name="self_fence">
+ <longdesc lang="en">
+ If set and unmounting the file system fails, the node will
+ immediately reboot. Generally, this is used in conjunction
+ with force-unmount support, but it is not required.
+ </longdesc>
+ <shortdesc lang="en">
+ Seppuku Unmount
+ </shortdesc>
+ <content type="boolean"/>
+ </parameter>
+
<parameter name="fsid">
<longdesc lang="en">
File system ID for NFS exports. This can be overridden
@@ -795,6 +807,15 @@
esac
fi
+ if [ -n "$mp" ]; then
+ case ${OCF_RESKEY_self_fence} in
+ $YES_STR) self_fence=$YES ;;
+ 1) self_fence=$YES ;;
+ *) self_fence="" ;;
+ esac
+ fi
+
+
#
# Always do this hackery on clustered file systems.
#
@@ -870,8 +891,13 @@
done # while
if [ -n "$umount_failed" ]; then
- ocf_log err "'umount $dev' failed ($mp), error=$ret_val"
+ ocf_log err "'umount $mp' failed, error=$ret_val"
+ if [ "$self_fence" ]; then
+ ocf_log alert "umount failed - REBOOTING"
+ sync
+ reboot -fn
+ fi
return $FAIL
fi
next reply other threads:[~2007-11-13 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 17:38 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-19 20:54 [Cluster-devel] cluster/rgmanager/src/resources clusterfs.sh lhh
2007-12-19 20:53 lhh
2007-12-05 17:42 lhh
2007-12-05 17:42 lhh
2006-11-27 22:12 lhh
2006-10-25 15:38 lhh
2006-10-20 20:58 lhh
2006-10-20 20:36 lhh
2006-10-16 14:39 lhh
2006-10-06 15:43 lhh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071113173802.28111.qmail@sourceware.org \
--to=lhh@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).