Thank you. I did same thing already - place nfs backup folder on same storage but in different path.
For now I just remember this bug and will wait for updates cause almost all VMs moved to the new cluster.
Thank you for explanation. But maybe it was not the problem which you described.
I mean - migration task of 101 VM started at night and throughout the night no one destroyed any VM on any nodes.
I could destroy another 101 VM on outside node, but early during the day. Is it somehow affected on...
If we talk about nodes outside the cluster with connection through NFS to cluster node with VM 101 - yes, few nodes actually.
I mean
outside node-1: VM 101 xxx
outside node-2: VM 101 yyy
cluster node: VM 101 zzz
But i reinstalled OS on them and cant give you any logs from that nodes.
Although...
It was the first time when I get problem like this. As i wrote before - there was a case when migration also failed with similar errors instead of deleting disks. There was no any NFS/CIFS storages.
Maybe i have some hardware problems because destination node are the same. But all IPMI/iLO...
I'll try it with next VMs cause current VM doesnt have any disks.
So, to be clear:
1) The error has occurred because:
a) pve-qemu-kvm: 5.1.0-8 version bug ?
b) pve-qemu-kvm difference between two nodes ?
c) something else?
2) Is it normal behavior with deletion disks on both nodes due migration...
I could not find any reasons of fails in guest logs of 101 VM. "Guests" means logs of particular 101 VM or some systemd pve services/another?
logs.zip:
UPID:gpsrv-hdd1:0000A117:04159A02:603B37BD:qmrestore:101:root@pam: - restore from backup...
Storage1 is just directory on all nodes.
mount
/dev/sda2 on /boot type ext4 (rw,relatime,stripe=1024)
/dev/sda3 on /mnt/storage1 type ext4 (rw,relatime,stripe=256)
/dev/sda6 on / type ext4 (rw,relatime,errors=remount-ro,stripe=256)
But indeed this directory shared by NFS for another nodes...
Good day!
I want to migrate running VM between 2 Proxmox nodes(10.105.2.29 -> 10.105.2.21), joined in cluster.
But migration task failed("VM 101 is not running") AND all VM disks were erased.
10.105.2.29
ls -la /mnt/storage1/images/101
total 8
drwxr----- 2 root root 4096 Feb 28 18:30 ...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.