From: bmarzins@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: multipath-tools ./multipath.conf.defaults libm ...
Date: 28 Sep 2009 18:28:49 -0000 [thread overview]
Message-ID: <20090928182849.11617.qmail@sourceware.org> (raw)
CVSROOT: /cvs/dm
Module name: multipath-tools
Branch: RHEL5_FC6
Changes by: bmarzins@sourceware.org 2009-09-28 18:28:48
Modified files:
. : multipath.conf.defaults
libmultipath : hwtable.c
Log message:
Fix for bz #504619. MSA 1000s with new firmware can't list the vendor as HP or COMPAQ, same as with the old firmware. Updated the default configuration to
match this.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/multipath.conf.defaults.diff?cvsroot=dm&only_with_tag=RHEL5_FC6&r1=1.5.4.15&r2=1.5.4.16
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/libmultipath/hwtable.c.diff?cvsroot=dm&only_with_tag=RHEL5_FC6&r1=1.20.2.21&r2=1.20.2.22
--- multipath-tools/multipath.conf.defaults 2009/08/19 21:52:40 1.5.4.15
+++ multipath-tools/multipath.conf.defaults 2009/09/28 18:28:48 1.5.4.16
@@ -71,7 +71,7 @@
# path_checker tur
# }
# device {
-# vendor "HP"
+# vendor "(COMPAQ|HP)"
# product "MSA VOLUME"
# getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
# prio_callout "/sbin/mpath_prio_alua %n"
--- multipath-tools/libmultipath/hwtable.c 2009/08/31 17:17:10 1.20.2.21
+++ multipath-tools/libmultipath/hwtable.c 2009/09/28 18:28:48 1.20.2.22
@@ -108,7 +108,7 @@
},
{
/* MSA 1000/1500 with new firmware */
- .vendor = "HP",
+ .vendor = "(COMPAQ|HP)",
.product = "MSA VOLUME",
.getuid = DEFAULT_GETUID,
.getprio = "/sbin/mpath_prio_alua /dev/%n",
next reply other threads:[~2009-09-28 18:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 18:28 bmarzins [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-14 21:56 multipath-tools ./multipath.conf.defaults libm bmarzins
2011-01-21 16:57 bmarzins
2010-11-12 20:17 bmarzins
2010-09-21 18:06 bmarzins
2010-09-14 19:42 bmarzins
2010-09-03 3:46 bmarzins
2010-08-24 21:51 bmarzins
2010-08-09 21:35 bmarzins
2010-08-09 18:38 bmarzins
2010-02-10 4:11 bmarzins
2010-01-26 5:50 bmarzins
2009-12-02 19:15 bmarzins
2009-09-28 18:41 bmarzins
2009-09-11 15:19 bmarzins
2009-08-19 21:52 bmarzins
2009-01-15 22:47 bmarzins
2009-01-13 22:26 bmarzins
2008-08-29 18:30 bmarzins
2008-07-12 17:36 bmarzins
2008-07-12 2:44 bmarzins
2008-07-12 0:07 bmarzins
2008-01-03 20:16 bmarzins
2007-10-09 21:48 bmarzins
2007-09-11 18:06 bmarzins
2007-08-14 18:08 bmarzins
2007-08-14 18:23 ` S. J. van Harmelen
2007-05-07 17:59 bmarzins
2006-12-19 22:51 bmarzins
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=20090928182849.11617.qmail@sourceware.org \
--to=bmarzins@sourceware.org \
--cc=dm-cvs@sourceware.org \
--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.