From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
christophe varoqui <christophe.varoqui@free.fr>,
device-mapper development <dm-devel@redhat.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: [PATCH] Reattach device handler for multipath devices
Date: Mon, 17 Nov 2008 12:29:55 +0100 [thread overview]
Message-ID: <492155B3.6030204@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Hi James, Aladair,
when using multipath the daemon might have specified
a different device handler than used by default.
(Eg Clariion in ALUA mode).
For these cases we currently cannot setup a multipath map
automatically as scsi_dh_attach() will fail.
Instead we should be trying to reattach with the correct
device handler and only return an error if that fails.
Please apply.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
[-- Attachment #2: dm-mpath-reattach-dh --]
[-- Type: text/plain, Size: 1798 bytes --]
Reattach device handler for multipath devices
The multipath daemon might have specified a different device_handler
than the one a device is attached to by default.
So we should try to re-attach with the user-specified device_handler
and only return an error if that fails.
Signed-off-by: Hannes Reinecke <hare@suse.de
diff --git a/drivers/md/dm-mpath.c b/drivers/md/dm-mpath.c
index 4840733..4e39966 100644
--- a/drivers/md/dm-mpath.c
+++ b/drivers/md/dm-mpath.c
@@ -592,9 +592,19 @@ static struct pgpath *parse_path(struct arg_set *as, struct path_selector *ps,
}
if (m->hw_handler_name) {
- r = scsi_dh_attach(bdev_get_queue(p->path.dev->bdev),
- m->hw_handler_name);
+ struct request_queue *q = bdev_get_queue(p->path.dev->bdev);
+
+ r = scsi_dh_attach(q, m->hw_handler_name);
+ if (r == -EBUSY) {
+ /*
+ * Already attached to different hw_handler,
+ * try to reattach with correct one.
+ */
+ scsi_dh_detach(q);
+ r = scsi_dh_attach(q, m->hw_handler_name);
+ }
if (r < 0) {
+ ti->error = "error attaching hardware handler";
dm_put_device(ti, p->path.dev);
goto bad;
}
diff --git a/drivers/scsi/device_handler/scsi_dh.c b/drivers/scsi/device_handler/scsi_dh.c
index a518f2e..f5d592f 100644
--- a/drivers/scsi/device_handler/scsi_dh.c
+++ b/drivers/scsi/device_handler/scsi_dh.c
@@ -504,12 +504,9 @@ void scsi_dh_detach(struct request_queue *q)
if (!sdev)
return;
- if (sdev->scsi_dh_data) {
- /* if sdev is not on internal list, detach */
- scsi_dh = sdev->scsi_dh_data->scsi_dh;
- if (!device_handler_match(scsi_dh, sdev))
- scsi_dh_handler_detach(sdev, scsi_dh);
- }
+ if (sdev->scsi_dh_data)
+ scsi_dh_handler_detach(sdev, sdev->scsi_dh_data->scsi_dh);
+
put_device(&sdev->sdev_gendev);
}
EXPORT_SYMBOL_GPL(scsi_dh_detach);
reply other threads:[~2008-11-17 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=492155B3.6030204@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=agk@redhat.com \
--cc=christophe.varoqui@free.fr \
--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