Comment # 3 on bug 1133795 from Martin Wilck

(In reply to Ruediger Oertel from comment #2)

> well, first of all because Johannes told me that the latency of multipath
> is by order of magnitude larger than the latency for nvme devices and there
> only is a single path to the device anyway....

Maybe, but that doesn't matter for multipath's policies. The udevadm shows that
this is a SUBSYSTEM=="nvme", which is supported and automatically activated
by multipathd.

You have several options to configure the desired behavior in multipath.conf:

a)

defaults {
   find_multipaths smart
}

(or "yes" instead of "smart")

b)

blacklist {
     protocol nvme
}

c)

blacklist {
     devnode "^nvme"
}

d)

blacklist {
    device {
        vendor NVME
        product ".*"
    }
}

Option a) causes multipathd to grab only devices with multiple paths. The
others are different ways to express that NVMe devices shouldn't be touched.

Remember to rebuild the intird when you change either setting.