Taking/rollback snapshot take a lot longer in Proxmox 6

[jenssen99]

Hello,

I recently updated to Proxmox 6, using the normal update guide from 5 to 6. I did an in-place upgrade, everything went very smooth. The only thing I know notice is that taking/rollback snapshots do take a lot longer, somtimes a few minutes, before it normally was done within seconds. Deleting a snapshot is still very quick. I am using normal local storage, no ceph, not running a cluster, only one node.

Anyone having any idea, or having the same issue?

Kind regards.

Hugo

 

[spirit]

what is your storage ? (lvm,rbd, zfs, qcow2 files,....)

 

[jenssen99]

what is your storage ? (lvm,rbd, zfs, qcow2 files,....)

Hello,

I am using SSD storage, LVM thin provioning, qcow2 files.

Last night, also my local Proxmox backup failed, hereby the logging (part of the logfile, the complete). Now I can not access the disks anymore via the GUI (to check summary/content/permissions for example), I receive a connection time out 596 message in the GUI after a while. The virtual machine running on the store, is still functioning ok. I never had this issue before on Proxmox 5.x

--
INFO: starting new backup job: vzdump --quiet 1 --mode snapshot --mailnotification failure --compress 0 --node proxmox --storage backup-sdc --all 1
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2019-08-08 03:00:02
INFO: status = running
INFO: update VM 101: -lock backup
INFO: VM Name: pfSense
INFO: include disk 'virtio0' 'local-lvm:vm-101-disk-1' 16G
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
ERROR: Backup of VM 101 failed - no such volume 'local-lvm:vm-101-disk-1'
INFO: Failed at 2019-08-08 03:00:29
INFO: Starting Backup of VM 102 (qemu)
INFO: Backup started at 2019-08-08 03:00:29
INFO: status = running
INFO: update VM 102: -lock backup
INFO: VM Name: OpenMediaVault
INFO: include disk 'virtio0' 'local-lvm:vm-102-disk-1' 16G
INFO: exclude disk 'virtio1' 'download-sdb:vm-102-disk-1' (backup=no)
INFO: exclude disk 'virtio2' 'media-sdh:vm-102-disk-1' (backup=no)
INFO: exclude disk 'virtio3' 'video-sda:vm-102-disk-1' (backup=no)
INFO: exclude disk 'virtio4' 'camera-sdd:vm-102-disk-1' (backup=no)
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
ERROR: Backup of VM 102 failed - no such volume 'local-lvm:vm-102-disk-1'
INFO: Failed at 2019-08-08 03:00:55
INFO: Starting Backup of VM 103 (qemu)
INFO: Backup started at 2019-08-08 03:00:55
INFO: status = stopped
INFO: update VM 103: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: ntop
INFO: include disk 'virtio0' 'vmct-sdf:vm-103-disk-1' 16G
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
ERROR: Backup of VM 103 failed - no such volume 'vmct-sdf:vm-103-disk-1'
INFO: Failed at 2019-08-08 03:01:22
INFO: Starting Backup of VM 104 (qemu)
INFO: Backup started at 2019-08-08 03:01:22
INFO: status = running
INFO: update VM 104: -lock backup
INFO: VM Name: VX9000
INFO: include disk 'virtio0' 'vmct-sdg:vm-104-disk-1' 20G
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
ERROR: Backup of VM 104 failed - no such volume 'vmct-sdg:vm-104-disk-1'
INFO: Failed at 2019-08-08 03:01:49
INFO: Starting Backup of VM 105 (qemu)
INFO: Backup started at 2019-08-08 03:01:49
INFO: status = running
INFO: update VM 105: -lock backup
INFO: VM Name: NSight
INFO: include disk 'virtio0' 'vmct-sdg:vm-105-disk-1' 20G
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/dm-56 not initialized in udev database even after waiting 10000000 microseconds.
ERROR: Backup of VM 105 failed - no such volume 'vmct-sdg:vm-105-disk-1'
INFO: Failed at 2019-08-08 03:02:15
INFO: Starting Backup of VM 106 (qemu)
INFO: Backup started at 2019-08-08 03:02:15
INFO: status = stopped

 

[jenssen99]

This looks more or less like the same issue?

https://forum.proxmox.com/threads/f...udev-database-even-after-waiting-10000.56814/

 

[inetshell]

Hi @jenssen99 , do you still have the problem? If yes, can you try executing this command?
# udevadm trigger

I had the same problem, and after a lot of research, I found that the cause was a failed restore I had some days back. I guess the failed backup created a DM device (/dev/dm-56 in your case) and proxmox did not clear the cache. The command "udevadm trigger" tells the kernel to send events for all the devices that are present. Another way could be to restart the host.

I don't know if this works in all cases, but in mine, worked as expected.

 

[gladiolah]

# udevadm trigger Helped me with the same issue after the actual update. Thanks a lot!

 

[jenssen99]

# udevadm trigger Helped me with the same issue after the actual update. Thanks a lot!

unfortunately does not help for me.

 

[shenxf2010]

Hi @jenssen99 , do you still have the problem? If yes, can you try executing this command?
# udevadm trigger

I had the same problem, and after a lot of research, I found that the cause was a failed restore I had some days back. I guess the failed backup created a DM device (/dev/dm-56 in your case) and proxmox did not clear the cache. The command "udevadm trigger" tells the kernel to send events for all the devices that are present. Another way could be to restart the host.

I don't know if this works in all cases, but in mine, worked as expected.

遇到同样的问题，使用此命令执行后，问题得到解决。