From: bmarzins@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: multipath-tools ./multipath.conf.defaults libm ...
Date: 9 Aug 2010 18:38:22 -0000 [thread overview]
Message-ID: <20100809183822.11463.qmail@sourceware.org> (raw)
CVSROOT: /cvs/dm
Module name: multipath-tools
Branch: RHEL5_FC6
Changes by: bmarzins@sourceware.org 2010-08-09 18:38:21
Modified files:
. : multipath.conf.defaults
libmultipath : hwtable.c
Log message:
Fix for bz #562967
It is now possible for all Symmetrix paths to go down on a NDU, so the config
needs to set no_path_retry.
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.20&r2=1.5.4.21
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/libmultipath/hwtable.c.diff?cvsroot=dm&only_with_tag=RHEL5_FC6&r1=1.20.2.27&r2=1.20.2.28
--- multipath-tools/multipath.conf.defaults 2010/02/10 04:11:18 1.5.4.20
+++ multipath-tools/multipath.conf.defaults 2010/08/09 18:38:21 1.5.4.21
@@ -233,9 +233,10 @@
# features "0"
# hardware_handler "0"
# path_grouping_policy multibus
+# no_path_retry 6
# rr_weight uniform
# rr_min_io 1000
-# path_checker readsector0
+# path_checker tur
# }
# device {
# vendor "EMC"
--- multipath-tools/libmultipath/hwtable.c 2010/02/10 04:11:18 1.20.2.27
+++ multipath-tools/libmultipath/hwtable.c 2010/08/09 18:38:21 1.20.2.28
@@ -223,9 +223,9 @@
.pgpolicy = MULTIBUS,
.pgfailback = FAILBACK_UNDEF,
.rr_weight = RR_WEIGHT_NONE,
- .no_path_retry = NO_PATH_RETRY_UNDEF,
+ .no_path_retry = 6,
.minio = DEFAULT_MINIO,
- .checker_name = READSECTOR0,
+ .checker_name = TUR,
},
{
.vendor = "DGC",
next reply other threads:[~2010-08-09 18:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 18:38 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-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-28 18:28 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=20100809183822.11463.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).