From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] gfs2: Panic when an io error occurs writing to the journal
Date: Mon, 17 Dec 2018 10:46:58 -0600 [thread overview]
Message-ID: <20181217164658.GA13933@redhat.com> (raw)
In-Reply-To: <1890286629.55916662.1545058727858.JavaMail.zimbra@redhat.com>
On Mon, Dec 17, 2018 at 09:58:47AM -0500, Bob Peterson wrote:
> Dave Teigland recommended. Unless I'm mistaken, Dave has said that GFS2
> should never withdraw; it should always just kernel panic (Dave, correct
> me if I'm wrong). At least this patch confines that behavior to a small
> subset of withdraws.
The basic idea is that you want to get a malfunctioning node out of the
way as quickly as possible so others can recover and carry on. Escalating
a partial failure into a total node failure is the best way to do that in
this case. Specialized recovery paths run from a partially failed node
won't be as reliable, and are prone to blocking all the nodes.
I think a reasonable alternative to this is to just sit in an infinite
retry loop until the i/o succeeds.
Dave
prev parent reply other threads:[~2018-12-17 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <142516811.55835189.1545054789753.JavaMail.zimbra@redhat.com>
2018-12-17 13:54 ` [Cluster-devel] [GFS2 PATCH] gfs2: Panic when an io error occurs writing to the journal Bob Peterson
2018-12-17 14:04 ` Edwin Török
2018-12-17 14:11 ` Steven Whitehouse
2018-12-17 14:58 ` Bob Peterson
2018-12-17 16:46 ` 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=20181217164658.GA13933@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.