[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [dm-devel] Wrong entries in hwtable.c for Hitachi Storage indevice-mapper-multipath-0.4.5-16.1.RHEL4.src.rpm



Hello Alasdair/All


The recommended entries for the HP Storageworks Arrays are as follows:
  	  r += store_hwe_ext(hw, "HP", "HSV101*", GROUP_BY_PRIO,
DEFAULT_GETUID,
                    "/sbin/mpath_prio_alua %n", "0","1
queue_if_no_path", "tur",
                    -FAILBACK_IMMEDIATE, NULL);
        r += store_hwe_ext(hw, "COMPAQ", "HSV111*", GROUP_BY_PRIO,
DEFAULT_GETUID,
                    "/sbin/mpath_prio_alua %n", "0", "1
queue_if_no_path", "tur",
                    -FAILBACK_IMMEDIATE, NULL);
        r += store_hwe_ext(hw, "HP", "HSV200", GROUP_BY_PRIO,
DEFAULT_GETUID,
                    "/sbin/mpath_prio_alua %n", "0", "1
queue_if_no_path", "tur",
                    -FAILBACK_IMMEDIATE, NULL);
        r += store_hwe_ext(hw, "HP", "HSV210", GROUP_BY_PRIO,
DEFAULT_GETUID,
                    "/sbin/mpath_prio_alua %n", "0", "1
queue_if_no_path", "tur",
                    -FAILBACK_IMMEDIATE, NULL);
        r += store_hwe_ext(hw, "HP", "OPEN-*", MULTIBUS, DEFAULT_GETUID,
NULL, "0", "0",
                    "tur", -FAILBACK_IMMEDIATE, NULL);

Currently HP recommends the above parameters in /etc/multipath.conf by
means of Configuration Guide for the HP Storageworks Arrays to override
the current default settings in hwtable.c.

Please let me know if any information needed further on this.

Thanks,
Anbu



-----Original Message-----
From: dm-devel-bounces redhat com [mailto:dm-devel-bounces redhat com]
On Behalf Of Matthias Rudolph
Sent: Wednesday, October 25, 2006 3:06 PM
To: dm-devel redhat com
Subject: [dm-devel] Wrong entries in hwtable.c for Hitachi Storage
indevice-mapper-multipath-0.4.5-16.1.RHEL4.src.rpm

Hi all,

I checked the latest dm-multipath in RHEL4U4 with Hitachi Storage
Arrays. Normally it should work now without a modified or created
/etc/multipath.conf. But it does not. I beliefe the file hwtable.c of
the source is not correct. The right entries on kernel.org did not found
the way to the RedHat package. Here my suggestions for file hwtable.c:

Wrong lines (please delete):
	r += store_hwe_ext(hw, "HP", "OPEN-.", MULTIBUS, DEFAULT_GETUID,
NULL,
		"0", "0", "tur", FAILBACK_UNDEF, NULL);
	r += store_hwe(hw, "HITACHI", "DF400", MULTIBUS,
DEFAULT_GETUID);
	r += store_hwe(hw, "HITACHI", "DF500", MULTIBUS,
DEFAULT_GETUID);
	r += store_hwe(hw, "HITACHI", "DF600", MULTIBUS,
DEFAULT_GETUID);
	r += store_hwe_ext(hw, "HITACHI", "DF600F*", GROUP_BY_PRIO,
		DEFAULT_GETUID, "/sbin/mpath/prio_hds_modular %d", "0",
"0",
 		"readsector0", -FAILBACK_IMMEDIATE, NULL);

Correct lines (please add):
	r += store_hwe_ext(hw, "{HITACHI,HP}", "OPEN-.*", MULTIBUS,
		DEFAULT_GETUID, NULL, "0", "0", "readsector0",
FAILBACK_UNDEF,
		NULL);
	r += store_hwe_ext(hw, "HITACHI", "DF.*", GROUP_BY_PRIO,
		DEFAULT_GETUID, "/sbin/mpath_prio_hds_modular %d", "0",
"0",
		"readsector0", -FAILBACK_IMMEDIATE, NULL);

I hope the regular expressions are correct for dm-multipath.
The file multipath.conf.defaults does also not match the entries in file
hwtable.c.

A temporary fix for the problem above is to create the file
/etc/multipath.conf with the entries below:

devices {
	device {
		vendor                  "HITACHI"
		product                 "DF.*"
		path_grouping_policy    group_by_prio
		prio_callout            "/sbin/pp_hds_modular %d"
		path_checker            readsector0
		getuid_callout          "/sbin/scsi_id -g -u -s
/block/%n"
		failback                immediate
		}
	device {
		vendor                  "HITACHI"
		product                 "OPEN-.*"
		path_grouping_policy    multibus
		path_checker            readsector0
		getuid_callout          "/sbin/scsi_id -g -u -s
/block/%n"
		}
	}


Regards
Matthias Rudolph

--
dm-devel mailing list
dm-devel redhat com
https://www.redhat.com/mailman/listinfo/dm-devel


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]