From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Chongyun Wu <wu.chongyun@h3c.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Cc: Guozhonghua <guozhonghua@h3c.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
Changwei Ge <ge.changwei@h3c.com>,
Changlimin <changlimin@h3c.com>, Martin Wilck <mwilck@suse.com>
Subject: Re: [PATCH] multipathd: check and cleanup zombie paths
Date: Fri, 9 Mar 2018 11:47:27 +0100 [thread overview]
Message-ID: <4d76e9a1-15bf-2bf4-c7dc-adf79b25e4a2@gmail.com> (raw)
In-Reply-To: <CEB9978CF3252343BE3C67AC9F0086A34295D215@H3CMLB14-EX.srv.huawei-3com.com>
On 03/09/2018 07:47 AM, Chongyun Wu wrote:
> You just mentioned *the TUR checker could return a special path state
> for this*, what is the special path state? Thanks~
to follow with this bug, you should post:
- distribution
- kernel release
- multipath-tools release
- /etc/multipath.conf
- and relevant system logs (multipath -v3 -d, journalctl, dmesg, messages, ...)
next prev parent reply other threads:[~2018-03-09 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CEB9978CF3252343BE3C67AC9F0086A34295C462@H3CMLB14-EX.srv.huawei-3com.com>
[not found] ` <1520325779.4131.4.camel@suse.com>
[not found] ` <CEB9978CF3252343BE3C67AC9F0086A34295C9D0@H3CMLB14-EX.srv.huawei-3com.com>
[not found] ` <1520349519.4131.20.camel@suse.com>
[not found] ` <CEB9978CF3252343BE3C67AC9F0086A34295CA7D@H3CMLB14-EX.srv.huawei-3com.com>
[not found] ` <1520426679.11340.5.camel@suse.com>
[not found] ` <CEB9978CF3252343BE3C67AC9F0086A34295CF62@H3CMLB14-EX.srv.huawei-3com.com>
2018-03-08 15:54 ` [PATCH] multipathd: check and cleanup zombie paths Xose Vazquez Perez
2018-03-09 6:11 ` Chongyun Wu
[not found] ` <20180308154435.GB14513@octiron.msp.redhat.com>
2018-03-09 6:47 ` Chongyun Wu
2018-03-09 10:47 ` Xose Vazquez Perez [this message]
2018-03-09 16:22 ` Benjamin Marzinski
2018-03-19 21:42 ` Martin Wilck
2018-03-20 3:19 ` Chongyun Wu
2018-03-20 7:36 ` Martin Wilck
2018-03-20 14:58 ` Bart Van Assche
2018-03-20 15:12 ` Xose Vazquez Perez
2018-03-20 15:14 ` Bart Van Assche
2018-03-20 15:19 ` Martin Wilck
2018-03-21 1:54 ` Chongyun Wu
2018-03-21 19:56 ` Bart Van Assche
2018-03-22 1:58 ` Chongyun Wu
2018-03-22 3:40 ` Chongyun Wu
2018-03-22 15:18 ` Bart Van Assche
2018-03-21 1:17 ` Chongyun Wu
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=4d76e9a1-15bf-2bf4-c7dc-adf79b25e4a2@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=changlimin@h3c.com \
--cc=dm-devel@redhat.com \
--cc=ge.changwei@h3c.com \
--cc=guozhonghua@h3c.com \
--cc=mwilck@suse.com \
--cc=wu.chongyun@h3c.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.