From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Linux SCSI Mailing list <linux-scsi@vger.kernel.org>
Cc: dm-devel <dm-devel@redhat.com>, "Moger, Babu" <Babu.Moger@lsi.com>
Subject: [PATCH] Make sure the state of a path is set properly when controller is swapped from passive to active
Date: Wed, 05 Nov 2008 20:05:21 -0800 [thread overview]
Message-ID: <1225944321.14830.1109.camel@chandra-ubuntu> (raw)
When the controller ownership is changed (from passive to active),
check_ownership() doesn't set the state of the device to ACTIVE.
This patch fixes the problem.
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Reported and tested by: "Moger, Babu" <Babu.Moger@lsi.com>
---
Index: linux-2.6.28-rc3/drivers/scsi/device_handler/scsi_dh_rdac.c
===================================================================
--- linux-2.6.28-rc3.orig/drivers/scsi/device_handler/scsi_dh_rdac.c
+++ linux-2.6.28-rc3/drivers/scsi/device_handler/scsi_dh_rdac.c
@@ -387,6 +387,7 @@ static int check_ownership(struct scsi_d
struct c9_inquiry *inqp;
h->lun_state = RDAC_LUN_UNOWNED;
+ h->state = RDAC_STATE_ACTIVE;
err = submit_inquiry(sdev, 0xC9, sizeof(struct c9_inquiry), h);
if (err == SCSI_DH_OK) {
inqp = &h->inq.c9;
next reply other threads:[~2008-11-06 4:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 4:05 Chandra Seetharaman [this message]
2008-11-10 23:17 ` [PATCH] scsi_dh: Adding LSI vendor and product ids in rdac device list Moger, Babu
2008-11-24 0:04 ` James Bottomley
2008-11-24 15:06 ` Moger, Babu
2008-11-11 0:45 ` DM does not activate the paths if there are more than one path in path group during failover Moger, Babu
2008-11-11 0:59 ` Alasdair G Kergon
2008-11-11 17:13 ` Moger, Babu
2008-11-11 21:00 ` Chandra Seetharaman
2008-11-13 23:48 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] DM does not activate the paths if there are more than one path in path group during failover") Chandra Seetharaman
2008-11-14 0:12 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 19:08 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-14 19:34 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 20:24 ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-11 2:06 ` DM does not activate the paths if there are more than one path in path group during failover Chandra Seetharaman
2008-11-11 17:07 ` Moger, Babu
2008-11-11 17:10 ` Chandra Seetharaman
2008-11-11 17:28 ` Moger, Babu
2009-01-22 0:00 ` qla2xxx 0000:03:0c.0: Firmware image unavailable Moger, Babu
2009-01-22 0:26 ` Seokmann Ju
2009-01-22 14:14 ` Moger, Babu
2009-01-22 14:39 ` Sudhakar Pannerselvam
2009-01-22 15:20 ` Moger, Babu
2009-01-22 16:46 ` Dave Holland
2009-01-23 0:15 ` [dm-devel] " Moger, Babu
2009-01-23 6:22 ` Sudhakar Pannerselvam
2009-01-23 15:04 ` James Bottomley
2009-01-25 4:22 ` Mike Snitzer
2009-01-22 14:56 ` James Bottomley
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=1225944321.14830.1109.camel@chandra-ubuntu \
--to=sekharan@us.ibm.com \
--cc=Babu.Moger@lsi.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/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