[PVE-User] LVM/pvesm udev database initialization warnings after import of KVM images

[Gianni Milo]

Does issuing 'udevadm trigger' helps?

On Fri, 10 Jan 2020 at 12:44, Frank Thommen <f.thommen at dkfz-heidelberg.de>
wrote:

> Dear all,
>
> after having (successfully) imported two KVM disk images from oVirt, LVM
> and pvesm complain about some udev initialization problem:
>
> root at pve01:~# pvesm status
>    WARNING: Device /dev/dm-8 not initialized in udev database even after
> waiting 10000000 microseconds.
>    WARNING: Device /dev/dm-9 not initialized in udev database even after
> waiting 10000000 microseconds.
>    WARNING: Device /dev/dm-8 not initialized in udev database even after
> waiting 10000000 microseconds.
>    WARNING: Device /dev/dm-9 not initialized in udev database even after
> waiting 10000000 microseconds.
> Name             Type     Status           Total            Used
> Available        %
> local             dir     active        98559220        45640836
> 47868836   46.31%
> local-lvm     lvmthin     active       832245760        71573135
> 760672624    8.60%
> root at pve01:~#
>
> root at pve01:~# lvdisplay
>    WARNING: Device /dev/dm-8 not initialized in udev database even after
> waiting 10000000 microseconds.
>    WARNING: Device /dev/dm-9 not initialized in udev database even after
> waiting 10000000 microseconds.
>    --- Logical volume ---
>    LV Path                /dev/pve/swap
>    LV Name                swap
>    VG Name                pve
>    [...]
> root at pve01:~#
>
> However this doesn't seem to influence the functionality of the VMs.
>
> Any idea what could be the problem and how to fix it?
>
> Thank you very much in advance
> Frank
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>