cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/2] fence_scsi: always do sg_turs before registration
Date: Fri, 21 Jan 2011 13:16:57 -0500	[thread overview]
Message-ID: <1295633817.857.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1295469047-29601-1-git-send-email-rohara@redhat.com>

On Wed, 2011-01-19 at 14:30 -0600, Ryan O'Hara wrote:
> If a node has been fenced, or its key has been forcibly removed from
> device(s) by another node, the victim will see "unit attention" from the
> devices if/when it attempts to re-register. This error is normally
> reported just once, but will cause registration to fail. We can safely
> avoid this by calling sg_turs prior to each attempt to register with a
> device.
> 
> Resolves: rhbz#640343

Reviewed; ack

-- Lon



      reply	other threads:[~2011-01-21 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 20:30 [Cluster-devel] [PATCH 2/2] fence_scsi: always do sg_turs before registration Ryan O'Hara
2011-01-21 18:16 ` Lon Hohberger [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=1295633817.857.14.camel@localhost.localdomain \
    --to=lhh@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).