From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fencing conditions: what should trigger a fencing operation?
Date: Fri, 20 Nov 2009 11:40:47 -0600 [thread overview]
Message-ID: <20091120174047.GA21348@redhat.com> (raw)
In-Reply-To: <4B0644C1.2020804@redhat.com>
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
prev parent reply other threads:[~2009-11-20 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 11:35 [Cluster-devel] fencing conditions: what should trigger a fencing operation? Fabio M. Di Nitto
2009-11-19 17:04 ` David Teigland
2009-11-19 16:15 ` Steven Whitehouse
2009-11-19 17:28 ` David Teigland
2009-11-19 17:16 ` David Teigland
2009-11-19 18:10 ` Fabio M. Di Nitto
2009-11-19 19:49 ` David Teigland
2009-11-20 7:26 ` Fabio M. Di Nitto
2009-11-20 17:40 ` David Teigland [this message]
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=20091120174047.GA21348@redhat.com \
--to=teigland@redhat.com \
/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).