Bug#1001710: multipath-tools: booting with lvm over multipath it does not setup devices for lvm

[Carlos Barros]

Package: multipath-tools
Version: 0.8.5-2
Severity: important
X-Debbugs-Cc: carlos.bar...@econocom.com

Dear Maintainer,

A server was setup with some disks configured in multipath.
The root filesystem is on LVM on internal disk, not configured for multipath.

Then build another lvm configuration on those devices (/dev/mapper/...)

Now, every time it starts, lvm takes the /dev/sd.. before multipath sets 
/dev/mapper/...  up.
Also, the booting proccess delays for 2+  minutes, mostly because of 
systemd-udev-settle.service:
        root@panblando:~# systemd-analyze blame
         2min 22ms systemd-udev-settle.service
        1min 105ms NetworkManager-wait-online.service
            9.983s smartmontools.service
            4.415s dev-mapper-dl380g8\x2d\x2dvg\x2droot.device

But this service is called from multipath:
        [Unit]
        Description=Device-Mapper Multipath Device Controller
        Wants=systemd-udev-trigger.service systemd-udev-settle.service
        Before=iscsi.service iscsid.service lvm2-activation-early.service
        Before=local-fs-pre.target blk-availability.service
        After=multipathd.socket systemd-udev-trigger.service 
systemd-udev-settle.service
        DefaultDependencies=no
        Conflicts=shutdown.target
        ConditionKernelCommandLine=!nompath
        ConditionKernelCommandLine=!multipath=off

According to systemd-udev-settle.service(8) it is not recommended, as that 
service can fail (in fact, 
in the server it fails as systemd says) 

I think that the problem is related to multipath, because it did not setup the 
devices before lvm, 
and maybe the problem is inside the initrd.

Then I did install multipath-tools-boot but the problem is the same.
The only way is to avoid mounting the filesystems in the LVM (or umounting 
them) vgchange -an VG 
and do the multipath and mount it, all by hand

The disk list in multipath is short (8 disks with only 1 path each by now)

Best regards,
Carlos Barros.

-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
        polling_interval 10
        user_friendly_names yes
}
blacklist {
        device {
                vendor "HP"
                product "LOGICAL VOLUME"        #HPSA raid internal
        }
}



-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages multipath-tools depends on:
ii  kpartx              0.8.5-2
ii  libaio1             0.3.112-9
ii  libc6               2.31-13+deb11u2
ii  libdevmapper1.02.1  2:1.02.175-2.1
ii  libjson-c5          0.15-2
ii  libreadline8        8.1-1
ii  libsystemd0         247.3-6
ii  libudev1            247.3-6
ii  liburcu6            0.12.2-1
ii  lsb-base            11.1.0
ii  sg3-utils-udev      1.45-1
ii  udev                247.3-6

multipath-tools recommends no packages.

Versions of packages multipath-tools suggests:
ii  multipath-tools-boot  0.8.5-2

-- no debconf information