From: Lars Marowsky-Bree <lmb@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] [multipath] SCSI device capacity mess
Date: Wed, 27 Oct 2004 10:42:02 +0200 [thread overview]
Message-ID: <20041027084202.GD32712@marowsky-bree.de> (raw)
In-Reply-To: <20041027081713.GC32712@marowsky-bree.de>
On 2004-10-27T10:17:13, Lars Marowsky-Bree <lmb@suse.de> wrote:
> Using the new priority group initialization code (where we sent magic
> commands down to activate the newly switched-to PG) which Alasdair and I
> are currently doing for the CLARiiON pampering and which provides a
> plugin-architecture to the dm-mpath system, you should be able to plug
> in a hardware-specific handler for your system too.
>
> However, "relaxing" this check should likely also be a property of the
> hardware plugin loaded; I'd not wish to have it relaxed in all
> scenarios.
-> have the hardware-specific plugin export a path_init() function which
is called the first time a path is added to the table (or even on
reinstate?).
In addition verifying the size and stuff it could also check that the
paths really (still) point to the same device (by storing the LUN WWN in
the hw_handler context, for example), or that the path is setup
correctly for failover to work etc (of course, the list of things to
verify is a hw-specific issue). Paranoia is a good thing.
Mit freundlichen Grüßen,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-10-27 17:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 23:27 [multipath] SCSI device capacity mess christophe varoqui
2004-10-26 21:34 ` James Bottomley
2004-10-26 21:46 ` christophe varoqui
2004-10-27 8:17 ` [dm-devel] " Lars Marowsky-Bree
2004-10-27 8:42 ` Lars Marowsky-Bree [this message]
2004-10-27 18:51 ` Bryan Henderson
2004-10-29 14:12 ` Lars Marowsky-Bree
2004-10-29 16:48 ` Bryan Henderson
2004-10-27 19:02 ` christophe varoqui
2004-10-27 19:37 ` Eddie Williams
2004-10-27 20:19 ` christophe varoqui
2004-10-27 20:34 ` Greg Freemyer
2004-10-27 20:28 ` Philip R Auld
2004-10-27 21:57 ` James Bottomley
2004-10-28 11:37 ` Lars Marowsky-Bree
2004-10-28 18:14 ` Patrick Mansfield
2004-10-28 18:21 ` Lars Marowsky-Bree
2004-10-30 0:41 ` Patrick Mansfield
2004-10-30 1:01 ` Patrick Mansfield
2004-10-30 7:21 ` christophe varoqui
2004-10-30 8:22 ` christophe varoqui
2004-11-02 15:23 ` Lars Marowsky-Bree
2004-10-28 11:35 ` Lars Marowsky-Bree
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=20041027084202.GD32712@marowsky-bree.de \
--to=lmb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).