From: Lars Marowsky-Bree <lmb@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Should multipath detect changed path UIDs?
Date: Wed, 26 Jan 2005 23:13:54 +0100 [thread overview]
Message-ID: <20050126221354.GX5511@marowsky-bree.de> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321A71C@SRMANNING.eng.emc.com>
On 2005-01-26T16:50:50, "goggin, edward" <egoggin@emc.com> wrote:
> Possible solutions could involve (1) detecting fiber channel disconnect
> hotplug events and acting upon them or (2) modifying multipath checker
> functions to verify a path's UID remains consistent in addition to verifying
> path connectivity.
If you look at the emc_clariion checker in multipath-tools, you'll find
it does that.
I've this handy paper called "Developing Multipath Software for EMC
CLARiiON Arrays" in front of me and believe that we implement it
already, as far as possible. ;-)
(There's one missing piece, it's handling the specific sense codes, but
you'll find that they are already coded in dm-emc.c in the kernel, just
disabled until we finally get the patch to get at the SCSI SENSE data in
the bio struct. I need to pester axboe about it again.)
Maybe you could add the Symmetrix specific handling to the emc_clariion
path checker and the dm-emc.c kernel module? I'd be glad to make it more
powerful than "just" the CX/AX arrays, alas, I "only" have a CX-500 for
playing with ;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2005-01-26 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 21:50 Should multipath detect changed path UIDs? goggin, edward
2005-01-26 22:13 ` Lars Marowsky-Bree [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 21:49 goggin, edward
2005-01-30 6:14 ` Tim Pepper
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=20050126221354.GX5511@marowsky-bree.de \
--to=lmb@suse.de \
--cc=dm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.