From: bmarzins@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: multipath-tools ./Multipath-usage.txt ./multip ...
Date: 10 Jan 2007 21:56:18 -0000 [thread overview]
Message-ID: <20070110215618.29313.qmail@sourceware.org> (raw)
CVSROOT: /cvs/dm
Module name: multipath-tools
Branch: RHEL4_FC5
Changes by: bmarzins@sourceware.org 2007-01-10 21:56:17
Modified files:
. : Multipath-usage.txt multipath.conf.defaults
libmultipath : hwtable.c
multipath : multipath.conf.redhat
Log message:
Resolves: bz 220643
Doc changes, to explain about using /dev/mapper devices to avoid the udev race
at boot and to help people figure out how to use dasd devices. Also, the
IBM:S/390 devices are again blacklisted by default.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/Multipath-usage.txt.diff?cvsroot=dm&only_with_tag=RHEL4_FC5&r1=1.4.2.1&r2=1.4.2.2
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/multipath.conf.defaults.diff?cvsroot=dm&only_with_tag=RHEL4_FC5&r1=1.5.2.1&r2=1.5.2.2
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/libmultipath/hwtable.c.diff?cvsroot=dm&only_with_tag=RHEL4_FC5&r1=1.16.2.5&r2=1.16.2.6
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/multipath/multipath.conf.redhat.diff?cvsroot=dm&only_with_tag=RHEL4_FC5&r1=1.5.2.1&r2=1.5.2.2
--- multipath-tools/Multipath-usage.txt 2006/06/06 18:04:08 1.4.2.1
+++ multipath-tools/Multipath-usage.txt 2007/01/10 21:56:17 1.4.2.2
@@ -219,6 +219,12 @@
After initial setup, all access to the multipathed storage should go through the
multipath device.
+When a multipath device is mounted at boot time , udev may not create the
+device node for it soon enough. To avoid this problem, instead of using
+the /dev/mpath/<device> name in /etc/fstab, use /dev/mapper/<device>. This
+device node is automatically created by device-mapper, as soon as the device is
+created.
+
GNBD devices will not be automatically multipathed after they are imported.
The command
--- multipath-tools/multipath.conf.defaults 2006/12/07 15:53:44 1.5.2.1
+++ multipath-tools/multipath.conf.defaults 2007/01/10 21:56:17 1.5.2.2
@@ -204,6 +204,7 @@
# device {
# vendor "IBM"
# product "S/390 DASD ECKD"
+# bl_product "S/390"
# path_grouping_policy multibus
# getuid_callout "/sbin/dasdview -j /dev/%n"
# path_checker directio
--- multipath-tools/libmultipath/hwtable.c 2006/12/01 23:45:18 1.16.2.5
+++ multipath-tools/libmultipath/hwtable.c 2007/01/10 21:56:17 1.16.2.6
@@ -70,7 +70,7 @@
"tur", -FAILBACK_IMMEDIATE, NULL, 0, 0, 0);
r += store_hwe_ext(hw, "IBM", "S/390 DASD ECKD", MULTIBUS,
"/sbin/dasdview -j /dev/%n", NULL, "0", "0",
- "directio", FAILBACK_UNDEF, NULL, 0, 0, 0);
+ "directio", FAILBACK_UNDEF, "S/390", 0, 0, 0);
r += store_hwe_ext(hw, "NETAPP", "LUN", GROUP_BY_PRIO, DEFAULT_GETUID,
"/sbin/mpath_prio_netapp /dev/%n", NULL,
"1 queue_if_no_path", "readsector0", FAILBACK_UNDEF, NULL, 0, 0, 0);
--- multipath-tools/multipath/multipath.conf.redhat 2007/01/04 19:02:30 1.5.2.1
+++ multipath-tools/multipath/multipath.conf.redhat 2007/01/10 21:56:17 1.5.2.2
@@ -15,6 +15,22 @@
defaults {
user_friendly_names yes
}
+
+
+## By default, devices with vendor = "IBM" and product = "S/390.*" are
+## blacklisted. To enable mulitpathing on these devies, uncomment the
+## following lines.
+#devices {
+# device {
+# vendor "IBM"
+# product "S/390 DASD ECKD"
+# path_grouping_policy multibus
+# getuid_callout "/sbin/dasdview -j /dev/%n"
+# path_checker directio
+# }
+#}
+
+
##
## This is a template multipath-tools configuration file
## Uncomment the lines relevent to your environment
next reply other threads:[~2007-01-10 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 21:56 bmarzins [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-02 20:24 multipath-tools ./Multipath-usage.txt ./multip 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=20070110215618.29313.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.