From: Eddie Williams <Eddie.Williams@steeleye.com>
To: sekharan@linux.vnet.ibm.com,
device-mapper development <dm-devel@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
SCSI development list <linux-scsi@vger.kernel.org>,
asson_ronald <asson_ronald@emc.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Mike Christie <mchristi@redhat.com>,
"Benoit, Arthur" <Benoit_Arthur@emc.com>
Subject: Re: [dm-devel] mechanism for multipath to pass information to hardware handler
Date: Fri, 26 Jun 2009 16:01:57 -0400 [thread overview]
Message-ID: <1246046517.6707.57.camel@eddie-laptop> (raw)
In-Reply-To: <1246045509.14164.33.camel@chandra-ubuntu>
The problem is easy to duplicate using sg_persist to register/reserve
paths to a Clariion array and then fail the active path. The "enable"
path will fail to become active when the HONOR RESERVATION flag is not
set. Given of course that you have a Clariion array handy...
One question I have asked EMC is in what situations would you NOT want
to set this bit?
I can test out any changes you make in my test rig and I can probably
get the folks in the EMC lab I work with to test it as well.
Eddie
On Fri, 2009-06-26 at 12:45 -0700, Chandra Seetharaman wrote:
> Yes, Mike Christie and I were aware of this and it was one of the issue
> we were trying to resolve before we pushed scsi_dh interface upstream.
> (It is little complicated as we need the parameters to be set per
> vendor-product tuple).
>
> The original code I ported to scsi_dh interface was from Ed Goggin(who
> was working for EMC then). IIRC, he was also aware of this issue.
>
> When we pushed scsi_dh interface, we did get few of the EMC folks (on
> Cc) to review/test the code and they did, and this issue was not seen as
> a problem.
>
> We wanted to get back to that issue sometime later, got busy with other
> things, and it disappeared from my list of things-to-do as the
> regression was not seen as an issue (till now :)... I will get back to
> it.
>
> chandra
>
> On Fri, 2009-06-26 at 14:10 -0500, James Bottomley wrote:
> > On Wed, 2009-06-24 at 13:14 -0400, Eddie Williams wrote:
> > > I notice in scsi_dh_emc.c that there is a comment:
> > >
> > > TODO: need some interface so we can set trespass values
> > >
> > > I don't see where any such interface has been developed or even any
> > > discussion on the different mailing lists to create such an interface.
> > > Did I miss something?
> > >
> > > As it stands now there is no way that I can see to have the emc hardware
> > > handler support the "honor trespass" feature short of recompiling the
> > > module forcing the flag to be set. This leaves a feature that worked in
> > > earlier versions of multipath not working now.
> >
> > OK so as I understand it that means that the line
> >
> > hardware handler "1 emc 0 1"
> >
> > now fails to function correctly because dm-emc no longer exists. That
> > makes this a functionality regression from 2.6.26 because of this
> > commit:
> >
> >
> > commit cb520223d7f22c5386aff27a5856a66e2c32aaac
> > Author: Chandra Seetharaman <sekharan@us.ibm.com>
> > Date: Thu May 1 14:50:34 2008 -0700
> >
> > [SCSI] scsi_dh: Remove hardware handlers from dm
> >
> > This patch removes the 3 hardware handlers that currently exist
> > under dm as the functionality is moved to SCSI layer in the earlier
> > patches.
> >
> > Because we haven't actually moved all the functionality.
> >
> > James
> >
> >
> >
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2009-06-26 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:14 mechanism for multipath to pass information to hardware handler Eddie Williams
2009-06-26 19:10 ` [dm-devel] " James Bottomley
2009-06-26 19:45 ` Chandra Seetharaman
2009-06-26 19:55 ` James Bottomley
2009-06-27 0:03 ` Chandra Seetharaman
2009-06-27 17:48 ` Mike Christie
2009-06-26 20:01 ` Eddie Williams [this message]
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=1246046517.6707.57.camel@eddie-laptop \
--to=eddie.williams@steeleye.com \
--cc=Benoit_Arthur@emc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=asson_ronald@emc.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=rjw@sisk.pl \
--cc=sekharan@linux.vnet.ibm.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