From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Teigland Date: Fri, 20 Nov 2009 11:40:47 -0600 Subject: [Cluster-devel] fencing conditions: what should trigger a fencing operation? In-Reply-To: <4B0644C1.2020804@redhat.com> References: <4B052D69.3010502@redhat.com> <20091119170404.GA23287@redhat.com> <4B058A2E.9070600@redhat.com> <20091119194952.GE23287@redhat.com> <4B0644C1.2020804@redhat.com> Message-ID: <20091120174047.GA21348@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Fri, Nov 20, 2009 at 08:26:57AM +0100, Fabio M. Di Nitto wrote: > We can?t take decision for OOPSes that are not generated within our > code. The user will have to configure that via panic_on_oops or other > means. Maybe our task is to make sure users are aware of this > situation/option (i didn?t check if it is documented). Yeah, in past we've told (and documented) people to set panic_on_oops=1 if it's not already set that way (see the gfs_mount man page I gave a link to for one example). As I said, in some releases, like RHEL4 and RHEL5, panic_on_oops is 1 by default, so everyone tends to forget about it. But I think upstream kernels currently default to 0, so this will bite people using upstream kernels who don't happen to read our documentation about setting the systctl. Dave