public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: rohara@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/fence/agents/scsi fence_scsi.pl
Date: Thu, 14 Dec 2006 21:16:00 -0000 [thread overview]
Message-ID: <20061214211636.12284.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: rohara@sourceware.org 2006-12-14 21:16:36
Modified files:
fence/agents/scsi: fence_scsi.pl
Log message:
Attempt to register the node in the case where it must perform fence_scsi
fencing but is not registered with the device(s) that must be fence. With
SCSI persistent reservations, in order to do a "preempt and abort" (which
we are using to fence a node), the node doing this operation must be
registered with the device. This fix will check to see the the node that
is performing the fencing is registered with the device(s). If it is not,
then it attempts to register with the device(s) so that it can then
continue with the fence operation normally. Note that this situation should
never happen, especially if things are configured properly.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/fence/agents/scsi/fence_scsi.pl.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.5.6.7&r2=1.5.6.8
next reply other threads:[~2006-12-14 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 21:16 rohara [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-21 3:09 rmccabe
2007-09-21 3:08 rmccabe
2006-12-14 21:18 rohara
2006-12-12 22:22 rohara
2006-12-12 22:22 rohara
2006-12-08 21:23 rohara
2006-12-07 20:04 rohara
2006-12-07 19:43 rohara
2006-12-07 19:40 rohara
2006-12-01 20:24 rohara
2006-12-01 17:53 rohara
2006-12-01 17:53 rohara
2006-11-29 23:19 rohara
2006-11-29 20:14 rohara
2006-07-12 20:34 rohara
2006-07-10 18:53 rohara
2006-07-06 21:58 rohara
2006-07-06 16:23 rohara
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=20061214211636.12284.qmail@sourceware.org \
--to=rohara@sourceware.org \
--cc=cluster-cvs@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).