From: Hannes Reinecke <hare@suse.de>
To: Steve Reilly <steve.reilly@hp.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 4/4] [libmultipath] Update hardware table forHPHSV200
Date: Wed, 15 Nov 2006 13:49:45 +0100 [thread overview]
Message-ID: <455B0CE9.8040103@suse.de> (raw)
In-Reply-To: <0E766B4D32E1BC4A877197B95A04A25A9F4FBF@tayexc14.americas.cpqcorp.net>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
Reilly, Stephen (MRO) wrote:
[ Quoting appears to be a lost art ... ]
>
> Hannes Reinecke wrote:
>> Reilly, Stephen (MRO) wrote:
>>> The product name does change if the firmware uses 'START_STOP_UNIT' or
>>> ALUA... so why are we adding the revision?
>>
>> Ah, that's news to me.
>> How does the product name change?
>
> The firmware will change the name
>
Oh, that's nice.
>> My contacts at HP Boeblingen said that the revision number indicated the
>> behaviour.
>> What are the names of the fw using START_STOP_UNIT?
> HSV100 and HSV110 EVA3000/5000
EVA is the name of the machine; HSV is the SCSI model name, right?
>> And what are those for using ALUA?
> HSV101, HSV111, HSV200 and HSV210 EVA 3000/5000 EVA4000/6000/8000
>
What about the old MSA ones? Is there a firmware upgrade available?
If so, will the name change there, too?
>> And irrespective of this I think matching by revision is still a valid
>> addition to the hardware table mechanism.
> However I would not use it determine the START_STOP_UNIT or ALUA implementation
>
I was under the impression that the name would stay the same. If that's
not the case then of course we should match onto the name.
Please check the attached patch if it updates the hwtables correctly.
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux Products GmbH S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
[-- Attachment #2: hp-hwtable-update --]
[-- Type: text/plain, Size: 2961 bytes --]
diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
index ac126c0..2fd6fac 100644
--- a/libmultipath/hwtable.c
+++ b/libmultipath/hwtable.c
@@ -75,21 +75,6 @@ static struct hwentry default_hw[] = {
.checker_name = HP_SW,
},
{
- .vendor = "(COMPAQ|HP)",
- .product = "(MSA|HSV)1.*",
- .getuid = DEFAULT_GETUID,
- .getprio = NULL,
- .features = DEFAULT_FEATURES,
- .hwhandler = "1 hp_sw",
- .selector = DEFAULT_SELECTOR,
- .pgpolicy = MULTIBUS,
- .pgfailback = FAILBACK_UNDEF,
- .rr_weight = RR_WEIGHT_NONE,
- .no_path_retry = NO_PATH_RETRY_UNDEF,
- .minio = DEFAULT_MINIO,
- .checker_name = HP_SW,
- },
- {
.vendor = "HP",
.product = "A6189A",
.getuid = DEFAULT_GETUID,
@@ -105,13 +90,13 @@ static struct hwentry default_hw[] = {
.checker_name = READSECTOR0,
},
{
- .vendor = "HP",
- .product = "HSV20.*",
- .revision = "[123].*",
+ /* EVA 3000/5000 with old firmware */
+ .vendor = "(COMPAQ|HP)",
+ .product = "(MSA|HSV)1.0.*",
.getuid = DEFAULT_GETUID,
.getprio = NULL,
.features = DEFAULT_FEATURES,
- .hwhandler = DEFAULT_HWHANDLER,
+ .hwhandler = "1 hp_sw",
.selector = DEFAULT_SELECTOR,
.pgpolicy = MULTIBUS,
.pgfailback = FAILBACK_UNDEF,
@@ -121,15 +106,15 @@ static struct hwentry default_hw[] = {
.checker_name = HP_SW,
},
{
- .vendor = "HP",
- .product = "HSV20.*",
- .revision = "[^123].*",
+ /* EVA 3000/5000 with new firmware */
+ .vendor = "(COMPAQ|HP)",
+ .product = "(MSA|HSV)1.1.*",
.getuid = DEFAULT_GETUID,
.getprio = "/sbin/mpath_prio_alua /dev/%n",
.features = DEFAULT_FEATURES,
.hwhandler = DEFAULT_HWHANDLER,
.selector = DEFAULT_SELECTOR,
- .pgpolicy = MULTIBUS,
+ .pgpolicy = GROUP_BY_PRIO,
.pgfailback = -FAILBACK_IMMEDIATE,
.rr_weight = RR_WEIGHT_NONE,
.no_path_retry = NO_PATH_RETRY_UNDEF,
@@ -137,15 +122,16 @@ static struct hwentry default_hw[] = {
.checker_name = TUR,
},
{
+ /* EVA 4000/6000/8000 */
.vendor = "HP",
- .product = "HSV21.*",
+ .product = "HSV2.*",
.getuid = DEFAULT_GETUID,
.getprio = "/sbin/mpath_prio_alua /dev/%n",
.features = DEFAULT_FEATURES,
.hwhandler = DEFAULT_HWHANDLER,
.selector = DEFAULT_SELECTOR,
.pgpolicy = GROUP_BY_PRIO,
- .pgfailback = FAILBACK_UNDEF,
+ .pgfailback = -FAILBACK_IMMEDIATE,
.rr_weight = RR_WEIGHT_NONE,
.no_path_retry = NO_PATH_RETRY_UNDEF,
.minio = DEFAULT_MINIO,
@@ -249,7 +235,7 @@ static struct hwentry default_hw[] = {
.rr_weight = RR_WEIGHT_NONE,
.no_path_retry = NO_PATH_RETRY_UNDEF,
.minio = DEFAULT_MINIO,
- .checker_name = READSECTOR0,
+ .checker_name = TUR,
},
{
.vendor = "HITACHI",
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-11-15 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061109221555.ED66173C93@hormel.redhat.com>
2006-11-13 19:44 ` [PATCH 4/4] [libmultipath] Update hardware table for HPHSV200 Reilly, Stephen (MRO)
2006-11-14 7:21 ` Hannes Reinecke
2006-11-15 12:10 ` [PATCH 4/4] [libmultipath] Update hardware table forHPHSV200 Reilly, Stephen (MRO)
2006-11-15 12:49 ` Hannes Reinecke [this message]
2006-11-16 13:42 ` Reilly, Stephen (MRO)
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=455B0CE9.8040103@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=steve.reilly@hp.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.