[PVE-User] LVM autoactivation failed with multipath over iSCSI

[Stefan M. Radman]

After upgrading a node that uses iSCSI multipath to 6.1, auto activation of LVM volumes fails for me as well.
I am seeing exactly the same problem as originally reported by Nada.

Apparently, LVM scans the iSCSI adapters before multipath is fully loaded and consequently ignores volumes appearing on duplicate devices.
Marco Gaiarin correctly noted this in January.

See the error messages in the system log below.

Does anyone have a hint, how to delay the lvm-pvscan service until multipath has finished its discovery?

Thanks

Stefan

Feb 02 22:31:25 proxmox kernel: device-mapper: multipath service-time: version 0.3.0 loaded
Feb 02 22:31:25 proxmox multipathd[1384]: 36000402002fc66d571e4e4cb00000000: load table [0 9766420480 multipath 1 queue_if_no_path 1 alua 1 1 service-time 0 1 1 8:64 1]
Feb 02 22:31:25 proxmox multipathd[1384]: sde [8:64]: path added to devmap 36000402002fc66d571e4e4cb00000000
Feb 02 22:31:25 proxmox kernel: sd 6:0:0:1: alua: port group 07 state N non-preferred supports tolusNA
Feb 02 22:31:25 proxmox kernel: sd 6:0:0:1: alua: port group 07 state N non-preferred supports tolusNA
Feb 02 22:31:25 proxmox systemd[1]: Starting LVM event activation on device 253:6...
Feb 02 22:31:26 proxmox iscsid[1946]: Connection1:0 to [target: iqn.1999-02.com.nexsan:p1:satabeast2:02a166d5, portal: 192.168.86.11,3260] through [iface: default] is operational now
Feb 02 22:31:26 proxmox iscsid[1946]: Connection2:0 to [target: iqn.1999-02.com.nexsan:p0:satabeast2:02a166d5, portal: 192.168.86.10,3260] through [iface: default] is operational now
Feb 02 22:31:26 proxmox iscsid[1946]: Connection3:0 to [target: iqn.1999-02.com.nexsan:p3:satabeast2:02a166d5, portal: 192.168.86.21,3260] through [iface: default] is operational now
Feb 02 22:31:26 proxmox iscsid[1946]: Connection4:0 to [target: iqn.1999-02.com.nexsan:p2:satabeast2:02a166d5, portal: 192.168.86.20,3260] through [iface: default] is operational now
Feb 02 22:31:26 proxmox lvm[2324]:   WARNING: Not using device /dev/sdb for PV EJCaTd-v9EY-vw8B-Bja1-bWdI-22Hf-1RL9cW.
Feb 02 22:31:26 proxmox lvm[2324]:   WARNING: Not using device /dev/sdc for PV EJCaTd-v9EY-vw8B-Bja1-bWdI-22Hf-1RL9cW.
Feb 02 22:31:26 proxmox lvm[2324]:   WARNING: Not using device /dev/sdd for PV EJCaTd-v9EY-vw8B-Bja1-bWdI-22Hf-1RL9cW.
Feb 02 22:31:26 proxmox lvm[2324]:   WARNING: PV EJCaTd-v9EY-vw8B-Bja1-bWdI-22Hf-1RL9cW prefers device /dev/mapper/36000402002fc66d571e4e4cb00000000 because device is in dm subsystem.
Feb 02 22:31:26 proxmox lvm[2324]:   Cannot activate LVs in VG san-vol1 while PVs appear on duplicate devices.
Feb 02 22:31:26 proxmox lvm[2324]:   Cannot activate LVs in VG san-vol1 while PVs appear on duplicate devices.
Feb 02 22:31:26 proxmox lvm[2324]:   Cannot activate LVs in VG san-vol1 while PVs appear on duplicate devices.
Feb 02 22:31:26 proxmox lvm[2324]:   0 logical volume(s) in volume group "san-vol1" now active
Feb 02 22:31:26 proxmox lvm[2324]:   san-vol1: autoactivation failed.
Feb 02 22:31:26 proxmox systemd[1]: lvm2-pvscan at 253:6.service: Main process exited, code=exited, status=5/NOTINSTALLED
Feb 02 22:31:26 proxmox systemd[1]: lvm2-pvscan at 253:6.service: Failed with result 'exit-code'.
Feb 02 22:31:26 proxmox systemd[1]: Failed to start LVM event activation on device 253:6.
Feb 02 22:31:26 proxmox multipathd[1384]: 36000402002fc66d571e4e4cb00000000: performing delayed actions
Feb 02 22:31:26 proxmox multipathd[1384]: 36000402002fc66d571e4e4cb00000000: load table [0 9766420480 multipath 1 queue_if_no_path 1 alua 2 1 service-time 0 2 1 8:32 1 8:16 1 service-time 0 2 1 8:64 1
Feb 02 22:31:26 proxmox kernel: sd 3:0:0:1: alua: port group 04 state A preferred supports tolusNA
Feb 02 22:31:26 proxmox kernel: sd 4:0:0:1: alua: port group 03 state A preferred supports tolusNA
Feb 02 22:31:26 proxmox kernel: sd 3:0:0:1: alua: port group 04 state A preferred supports tolusNA
Feb 02 22:31:26 proxmox kernel: sd 4:0:0:1: alua: port group 03 state A preferred supports tolusNA



CONFIDENTIALITY NOTICE: This communication may contain privileged and confidential information, or may otherwise be protected from disclosure, and is intended solely for use of the intended recipient(s). If you are not the intended recipient of this communication, please notify the sender that you have received this communication in error and delete and destroy all copies in your possession.