From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: no_path_retry: NO_PATH_RETRY_FAIL vs NO_PATH_RETRY_UNDEF
Date: Mon, 7 Nov 2016 12:55:20 -0600 [thread overview]
Message-ID: <20161107185520.GM1972@octiron.msp.redhat.com> (raw)
In-Reply-To: <de9f8dce-c3d4-b371-6c99-5cf9226d8f09@gmail.com>
On Mon, Nov 07, 2016 at 05:11:33PM +0100, Xose Vazquez Perez wrote:
> Hi,
>
>
> NO_PATH_RETRY_UNDEF is 0
>
>
> no_path_retry Specify what to do when all paths are down. Possible values are:
>
> value > 0 number of retries until disable I/O queueing.
>
> fail for immediate failure (no I/O queueing).
>
> queue for never stop I/O queueing. Similar to queue_if_no_path.
>
>
>
> Is there any real difference?
The idea was that if you have NO_PATH_RETRY_UNDEF, then you just use
whatever is in the features line. If you have NO_PATH_RETRY_FAIL, that
takes priority over the features line.
So if someone has
features "1 queue_if_no_path"
then NO_PATH_RETRY_UNDEF gets you the same results as
NO_PATH_RETRY_QUEUE.
-Ben
>
>
> Thank you.
prev parent reply other threads:[~2016-11-07 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 16:11 no_path_retry: NO_PATH_RETRY_FAIL vs NO_PATH_RETRY_UNDEF Xose Vazquez Perez
2016-11-07 18:55 ` Benjamin Marzinski [this message]
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=20161107185520.GM1972@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=xose.vazquez@gmail.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).