From: Martin Wilck <mwilck@suse.com>
To: Guan Junxiong <guanjunxiong@huawei.com>,
dm-devel@redhat.com, christophe.varoqui@opensvc.com,
hare@suse.de, bmarzins@redhat.com, xose.vazquez@gmail.com
Cc: chengjike.cheng@huawei.com, niuhaoxin@huawei.com, shenhong09@huawei.com
Subject: Re: [PATCH v3] multipath-tools: intermittent IO error accounting to improve reliability
Date: Tue, 05 Sep 2017 20:29:26 +0200 [thread overview]
Message-ID: <1504636166.4516.5.camel@suse.com> (raw)
In-Reply-To: <ab1527fa-c2e5-85d0-8285-231b38076274@huawei.com>
On Tue, 2017-09-05 at 10:59 +0800, Guan Junxiong wrote:
> Hi Martin,
> Thanks for you remarks and compiling check.
> An new patch will be updated in this week.
> Other response is inline.
>
> Cheers
> Guan Junxiong
>
> On 2017/9/5 4:59, Martin Wilck wrote:
> > map_discovery (struct vectors * vecs)
> > > {
> > > struct multipath * mpp;
> > > @@ -1134,6 +1170,7 @@ uev_trigger (struct uevent * uev, void *
> > > trigger_data)
> > > if (!strncmp(uev->kernel, "dm-", 3)) {
> > > if (!strncmp(uev->action, "change", 6)) {
> > > r = uev_add_map(uev, vecs);
> > > + uev_pathfail_check(uev, vecs);
> > > goto out;
> > > }
> > > if (!strncmp(uev->action, "remove", 6)) {
> >
> > It's interesting that you have chosen to act on kernel PATH_FAILED
> > events here. The existing multipath-tools code doesn't do that, it
> > relies on its internal state information (pathinfo, checkers)
> > instead.
> > I am not saying that what you're doing is wrong, but it deserves
> > some
> > explanation.
> >
> > Regards
> > Martin
> >
>
> the kernel PATH_FAILED events will only be issued when path IO error
> occours.
Are you positive about that? I thought I could swear that've seen those
for path deletion.
I need to double-check.
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2017-09-05 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 14:06 [PATCH v3] multipath-tools: intermittent IO error accounting to improve reliability Guan Junxiong
2017-09-04 20:59 ` Martin Wilck
2017-09-05 2:59 ` Guan Junxiong
2017-09-05 18:29 ` Martin Wilck [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=1504636166.4516.5.camel@suse.com \
--to=mwilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=chengjike.cheng@huawei.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=guanjunxiong@huawei.com \
--cc=hare@suse.de \
--cc=niuhaoxin@huawei.com \
--cc=shenhong09@huawei.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 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.