From: lhh@sourceware.org <lhh@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/rgmanager ChangeLog src/resources/clus ...
Date: 25 Sep 2007 13:23:47 -0000 [thread overview]
Message-ID: <20070925132347.21709.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: lhh at sourceware.org 2007-09-25 13:23:47
Modified files:
rgmanager : ChangeLog
rgmanager/src/resources: clusterfs.sh
Log message:
Resolve #252241 - add self_fence support to clusterfs
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/ChangeLog.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.5.2.29&r2=1.5.2.30
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/rgmanager/src/resources/clusterfs.sh.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.1.2.13&r2=1.1.2.14
--- cluster/rgmanager/ChangeLog 2007/07/31 18:26:39 1.5.2.29
+++ cluster/rgmanager/ChangeLog 2007/09/25 13:23:47 1.5.2.30
@@ -1,3 +1,6 @@
+2007-10-25 Lon Hohberger <lhh@redhat.com>:
+ * src/resources/clusterfs.sh: Make self_fence work. #252241
+
2007-07-31 Lon Hohberger <lhh@redhat.com>
* src/daemons/groups.c, rg_thread.c: Fix #246669 - status check unbounded
but should be 1
--- cluster/rgmanager/src/resources/clusterfs.sh 2007/05/21 15:56:47 1.1.2.13
+++ cluster/rgmanager/src/resources/clusterfs.sh 2007/09/25 13:23:47 1.1.2.14
@@ -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-09-25 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 13:23 lhh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-30 20:06 [Cluster-devel] cluster/rgmanager ChangeLog src/resources/clus lhh
2007-04-19 19:54 lhh
2007-04-19 19:53 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=20070925132347.21709.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).