Re: [dm-devel] [PATCH] multipath-tools: don't discard uevent for NVMe-Fabrics device

2017-07-14 Thread Martin Wilck
On Fri, 2017-07-14 at 18:49 +0800, Guan Junxiong wrote: > > I haven't seen your another patch since yesterday. So I update a new > patch > in the following. Does it looks good for you ? If so, I will send it > out formally. I've been testing my patch. Will send it ASAP. -- Dr. Martin Wilck

Re: [dm-devel] [PATCH] multipath-tools: don't discard uevent for NVMe-Fabrics device

2017-07-14 Thread Guan Junxiong
Hi,Martin: On 2017/7/13 18:04, Martin Wilck wrote: > On Thu, 2017-07-13 at 15:47 +0800, Guan Junxiong wrote: >> The devpath of uevent of NVMe-Fabrics device is like this >> "../devices/virtual/nvme-fabrics/ctl/nvme0/nvme0n1" which >> doesn't contains the "/block/" string. So when new uvents >> of

Re: [dm-devel] [PATCH] multipath-tools: don't discard uevent for NVMe-Fabrics device

2017-07-13 Thread Martin Wilck
On Thu, 2017-07-13 at 15:47 +0800, Guan Junxiong wrote: > The devpath of uevent of NVMe-Fabrics device is like this > "../devices/virtual/nvme-fabrics/ctl/nvme0/nvme0n1" which > doesn't contains the "/block/" string. So when new uvents > of such nvme devices arise, the multipathd daemon still

[dm-devel] [PATCH] multipath-tools: don't discard uevent for NVMe-Fabrics device

2017-07-13 Thread Guan Junxiong
The devpath of uevent of NVMe-Fabrics device is like this "../devices/virtual/nvme-fabrics/ctl/nvme0/nvme0n1" which doesn't contains the "/block/" string. So when new uvents of such nvme devices arise, the multipathd daemon still ignores them, which results the DM-multipath doesn't update the