From: Ryan O'Hara <rohara@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] fence_scsi: always do sg_turs before registration
Date: Mon, 24 Jan 2011 14:57:12 -0600 [thread overview]
Message-ID: <20110124205711.GD17856@redhat.com> (raw)
In-Reply-To: <1295902307.4673.6230.camel@ayanami.boston.devel.redhat.com>
On Mon, Jan 24, 2011 at 03:51:47PM -0500, Lon Hohberger wrote:
> On Mon, 2011-01-24 at 12:57 -0600, Ryan O'Hara wrote:
> > This patch fixes a with the original patch posted last week. Before
> > attempting to register with a device, we should call sg_turs on the
> > device. If that device is a dm-multipath device, we should call sg_turs
> > on all the paths. This can be done by simply moving the call to do_reset
> > to do_register and do_register_ignore.
> >
> > Also, the patch adds a call to do_reset before doing a "status" action.
> > If a node has been fenced and then proceeds to check its status, it will
> > be in "unit attention" state.
> >
> > Resolves: rhbz#640343
>
> Was reusing the same patch synopsis intentional here? It doesn't look
> like a replacement of the patch; it looks like an additional patch.
>
> -- Lon
Not intentional, no. Its the same bug, and the 2nd patch is just a
tweak to the first patch so that is properly resets all paths for
dm-mp devices.
Sorry for any confusion.
Ryan
prev parent reply other threads:[~2011-01-24 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 18:57 [Cluster-devel] [PATCH] fence_scsi: always do sg_turs before registration Ryan O'Hara
2011-01-24 20:51 ` Lon Hohberger
2011-01-24 20:57 ` Ryan O'Hara [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=20110124205711.GD17856@redhat.com \
--to=rohara@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.