[PVE-User] Cloning to other node fails
Sten Aus
sten.aus at eenet.ee
Mon May 9 08:46:20 CEST 2016
Hi
I don’t know if this has been patched/fixed in Proxmox 4.x version, but
in 3.4 I’ve managed to get a situation where I clone a VM on a node A to
a node B and when cloning is almost finished I get an error:
|transferred: 34365964288 bytes remaining: 0 bytes total: 34365964288
bytes progression: 100.00 % busy: false ready: true device-mapper:
remove ioctl on failed: Device or resource busy /--- multiple times same
message ---/ device-mapper: remove ioctl on failed: Device or resource
busy can't deactivate LV '/dev/virtuaalid/vm-185-disk-1': Unable to
deactivate virtuaalid-vm--185--disk--1 (253:11) Logical volume
"vm-198-disk-1" successfully removed TASK ERROR: clone failed: volume
deativation failed: voluum1:vm-185-disk-1 at
/usr/share/perl5/PVE/Storage.pm line 869. |
ID=185 is the source VM and 198 is the target (new, cloned) VM.
If I clone within the same VM, everything is OK and cloning process is
finished with no error.
ISCSI storage, LVMs, as you can see.
More information about the pve-user
mailing list