From: "Diedrich Ehlerding" <diedrich.ehlerding@ts.fujitsu.com>
To: dm-devel@redhat.com
Subject: [multipath] meaning of "no_path_retry nn"
Date: Fri, 28 Aug 2009 15:16:17 +0200 [thread overview]
Message-ID: <7ujn84$746nl@dgate20u.abg.fsc.net> (raw)
I would appreciate an explanation of "no_path_retry nn" parameter in
multipath.conf. Probably I misunderstood it as a number of seconds.
I am setting up a software mirror (mdadm) on top of an EMC Clariion
configuration for desaster protection. The Clariions are recognized by
multipath properly; it seems to be set up with "no_path_retry 60"
(according to multipath -t). I had no further settings in
multipath.conf; this seems to be hardcoded into multipath.
However, If I disconnect one Clariion, th mirror doesnt break -
multipath detects that all paths are failed and tells me that it will
now wait for 60 retries. These 60 retries seem to last very long;
atfter 5 minutes, it didnt complete.
Evertyhing works fine if I set up a multipath.conf containing the
Clariion settings from multipath -t and modify them to
"no_path_retry fail" and "features 0 fail_if_no_path". But even if I
just reduce the default settings to no_path_retry 2 the mirror doesnt
break - the IOs seem to hang indefinitely (well, I lost patience after
~5 minutes).
Probably I misunderstood "no_path_retry 60" - does that mean seconds,
or minutes, or what else? Is anything except "fail" a useful setting in
mirrored configurations?
system is a Suse with multipath-tools-0.4.7-34.43
Thanks
Diedrich
--
Diedrich Ehlerding, Fujitsu Technology Solutions GmbH, R GE TIS N IC2
Hildesheimer Str 25, D-30880 Laatzen
Fon +49 511 8489-1806, Fax -251806, Mobil +49 173 2464758
Firmenangaben: http://de.ts.fujitsu.com/imprint.html
next reply other threads:[~2009-08-28 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 13:16 Diedrich Ehlerding [this message]
2009-08-28 15:42 ` [multipath] meaning of "no_path_retry nn" Moger, Babu
2009-09-07 14:43 ` Hannes Reinecke
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='7ujn84$746nl@dgate20u.abg.fsc.net' \
--to=diedrich.ehlerding@ts.fujitsu.com \
--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