No, normally it's not required to do that. It appears that some people have had this issue when migrating a VM from raw to thin lvm (?), see the link below for more information...
https://forum.proxmox.com/threads/error-clone-failed-command-sbin-lvs-separator-noheadings-got-timeout.52519/#post-261766 It's unclear what is causing this. Perhaps an unfinished backup restore/clone job? Better to do some further tests, for example by creating a blank thin lvm based VM and see if the issue persists. G. On Fri, 10 Jan 2020 at 15:47, Frank Thommen <f.thom...@dkfz-heidelberg.de> wrote: > yes it did. Thank you very much. > > Is this a step that normally has to be executed after having imported a > disk image? If yes, then this could perhaps be added to > https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Qemu.2FKVM > . > > Cheers > frank > > > On 1/10/20 3:32 PM, Gianni Milo wrote: > > Does issuing 'udevadm trigger' helps? > > > > On Fri, 10 Jan 2020 at 12:44, Frank Thommen < > f.thom...@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@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@pve01:~# > >> > >> root@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@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@pve.proxmox.com > >> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >> > > _______________________________________________ > > pve-user mailing list > > pve-user@pve.proxmox.com > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user