Jeniffer, My previous assumption was wrong, the actual/current devmaps are indeed missing paths.
So the devmaps included in the first command/path discovery probably referred to the devmaps intended to be created (which were complete), but for some reason some paths failed to make it to the devmaps. Thus I'll ask you to collect an actual / non-dryrun log this time with extra libdevmapper verbosity. This will attempt to update the devmaps, so please ensure nothing is using/relying on them (e.g., mounted filesystems, swap devices, other applications accessing them directly for storage.) # multipath -v8 > multipath-v8-update.log 2>&1 Also, if there's nothing using/relying on these multipath devices in your system, we should probably check the devmaps _creation_ too (not just the _updates_ above.) So, if at all possible, after the above output has been collected already, I'd like to ask you to flush them all (so the devmaps and /dev/mapper/ devices are removed), and recreate them from scratch, to check if there are behavior differences to note. # multipath -v8 -F 2>&1 | tee multipath-v8-F.log # flush all devmaps # multipath -v8 -l 2>&1 | tee multipath-v8-l.log # confirm there are no multipath devices listed. # multipath -v8 > multipath-v8-create.log 2>&1 Thanks, Mauricio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860587 Title: multipath -ll doesn't discover down all paths on Emulex hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1860587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
