From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: tang.junhui@zte.com.cn
Cc: dm-devel@redhat.com, zhang.kai16@zte.com.cn, bart.vanassche@sandisk.com
Subject: Re: [PATCH] multipathd: fail path when path check timeout
Date: Tue, 11 Oct 2016 21:54:25 -0500 [thread overview]
Message-ID: <20161012025425.GD1972@octiron.msp.redhat.com> (raw)
In-Reply-To: <OF8F7422C1.AAA99072-ON48258049.002567ED-48258049.00258956@zte.com.cn>
On Tue, Oct 11, 2016 at 02:50:00PM +0800, tang.junhui@zte.com.cn wrote:
> Please have a review for this patch, any comment will be highly
> appreciated.
This is clearly correct. I suspect that there will be other places where
we need to also check for PATH_TIMEOUT, since it is basically the same
as PATH_DOWN, except with a different state name. For instance, we
only log error messages on repeated checks for (newstate == PATH_DOWN),
and we should probably do that for PATH_TIMEOUT as well. There are
probably more instances outside of check_path.
-Ben
>
> ������: tang.junhui@zte.com.cn
> �ռ���: christophe varoqui <christophe.varoqui@free.fr>,
> ����: dm-devel@redhat.com, zhang.kai16@zte.com.cn, "tang.junhui"
> <tang.junhui@zte.com.cn>
> ����: 2016/08/10 16:11
> ����: [PATCH] multipathd: fail path when path check timeout
>
> --------------------------------------------------------------------------
>
> From: "tang.junhui" <tang.junhui@zte.com.cn>
>
> path should be failed when path status is PATH_TIMEOUT after check,
> otherwise, the valid number of paths in the map would be increased when
> the path status is PATH_UP after the next turn check, which would cause
> the valid number of paths exceeding the total number of paths in the map.
>
> Signed-off-by: tang.junhui <tang.junhui@zte.com.cn>
> ---
> multipathd/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/multipathd/main.c b/multipathd/main.c
> index f5e9a01..01f1e58 100644
> --- a/multipathd/main.c
> +++ b/multipathd/main.c
> @@ -1585,7 +1585,7 @@ check_path (struct vectors * vecs, struct path * pp,
> int ticks)
> pp->checkint = conf->checkint;
> put_multipath_config(conf);
>
> - if (newstate == PATH_DOWN || newstate
> == PATH_SHAKY) {
> + if (newstate == PATH_DOWN || newstate
> == PATH_SHAKY || newstate == PATH_TIMEOUT) {
> /*
> * proactively fail
> path in the DM
> */
> --
> 2.8.1.windows.1
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2016-10-12 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 8:10 [PATCH] multipathd: fail path when path check timeout tang.junhui
2016-10-11 6:50 ` tang.junhui
2016-10-11 6:55 ` Christophe Varoqui
2016-10-12 2:54 ` Benjamin Marzinski [this message]
2016-10-12 3:20 ` tang.junhui
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=20161012025425.GD1972@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=tang.junhui@zte.com.cn \
--cc=zhang.kai16@zte.com.cn \
/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.