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

Stefan M. Radman smr at kmi.com
Tue Jan 14 19:46:29 CET 2020


Hi Nada

What's the output of "systemctl --failed" and "systemctl status lvm2-activation-net.service".

Stefan

> On Jan 14, 2020, at 16:40, nada <nada at verdnatura.es> wrote:
> 
> dont'worry and be happy Marco
> that rc.local save the situation (temporal solution ;-)
> and CTs which have resources on that 'santest' LV are auto started after reboot
> Nada
> 
> On 2020-01-14 16:12, Marco Gaiarin wrote:
>> Mandi! nada
>>  In chel di` si favelave...
>>> root at mox11:~# grep santest /var/log/syslog
>>> Jan 14 15:36:09 mox11 blkdeactivate[19162]:   [LVM]: deactivating Volume Group santest... skipping
>>> Jan 14 15:39:36 mox11 lvm[2086]:   Cannot activate LVs in VG santest while PVs appear on duplicate devices.
>>> Jan 14 15:39:36 mox11 lvm[2086]:   Cannot activate LVs in VG santest while PVs appear on duplicate devices.
>>> Jan 14 15:39:36 mox11 lvm[2086]:   0 logical volume(s) in volume group "santest" now active
>>> Jan 14 15:39:36 mox11 lvm[2086]:   santest: autoactivation failed.
>> Mmmhhhh... seems to me that LVM get activated before multipath, and so
>> they see multiple PVs (as effectively is).
>> Never happened before, sorry...
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpve.proxmox.com%2Fcgi-bin%2Fmailman%2Flistinfo%2Fpve-user&data=02%7C01%7Csmr%40kmi.com%7C80d026394e75434213c808d7990809b1%7Cc2283768b8d34e008f3d85b1b4f03b33%7C0%7C1%7C637146132119844345&sdata=9zp3vch%2FmXON%2FjJoIzCfnAc1w1bL%2BdvAKO7%2FARverHM%3D&reserved=0



More information about the pve-user mailing list