Hello.
I am in the process of converting our infrastructure from VMware to PVE and almost done. I'm now transferring the last bigger VMS.
Especially for one VM the following error occured the third time:
After failing everything is deleted. I also tried importing only the disks to a preconfigured VM, which worked for the first disk, but not for the second big one.
I migrated around 15 similar VMs (two disks) and have only seen this problem once, where a second try with another VM-ID solved the issue. This did not work for this VM.
I searched the forum and found an older issue pointing to pvs/lvs being wrongly active, but this doesn't seem to be the case here:
Version Info:
The import runs from an SSHFS mount onto a FibreChannel attached SAN storage.
I am in the process of converting our infrastructure from VMware to PVE and almost done. I'm now transferring the last bigger VMS.
Especially for one VM the following error occured the third time:
Code:
qm importovf 130 /vmwarestore/NewRepositoryServer/NewRepositoryServer.ovf san3
WARNING: dos signature detected on /dev/san3/vm-130-disk-0 at offset 510. Wipe it? [y/n]: [n]
Aborted wiping of dos.
Logical volume "vm-130-disk-0" created.
1 existing signature left on the device.
transferred: 0 bytes remaining: 21474836480 bytes total: 21474836480 bytes progression: 0.00 %
transferred: 214748364 bytes remaining: 21260088116 bytes total: 21474836480 bytes progression: 1.00 %
transferred: 429496729 bytes remaining: 21045339751 bytes total: 21474836480 bytes progression: 2.00 %
transferred: 644245094 bytes remaining: 20830591386 bytes total: 21474836480 bytes progression: 3.00 %
[...]
transferred: 21047487234 bytes remaining: 427349246 bytes total: 21474836480 bytes progression: 98.01 %
transferred: 21262235598 bytes remaining: 212600882 bytes total: 21474836480 bytes progression: 99.01 %
transferred: 21474836480 bytes remaining: 0 bytes total: 21474836480 bytes progression: 100.00 %
transferred: 21474836480 bytes remaining: 0 bytes total: 21474836480 bytes progression: 100.00 %
WARNING: LVM2_member signature detected on /dev/san3/vm-130-disk-1 at offset 536. Wipe it? [y/n]: [n]
Aborted wiping of LVM2_member.
Logical volume "vm-130-disk-1" created.
1 existing signature left on the device.
transferred: 0 bytes remaining: 1099511627776 bytes total: 1099511627776 bytes progression: 0.00 %
transferred: 10995116277 bytes remaining: 1088516511499 bytes total: 1099511627776 bytes progression: 1.00 %
transferred: 21990232555 bytes remaining: 1077521395221 bytes total: 1099511627776 bytes progression: 2.00 %
transferred: 32985348833 bytes remaining: 1066526278943 bytes total: 1099511627776 bytes progression: 3.00 %
transferred: 43980465111 bytes remaining: 1055531162665 bytes total: 1099511627776 bytes progression: 4.00 %
[...]
transferred: 1077521395220 bytes remaining: 21990232556 bytes total: 1099511627776 bytes progression: 98.00 %
transferred: 1088516511498 bytes remaining: 10995116278 bytes total: 1099511627776 bytes progression: 99.00 %
transferred: 1099511627776 bytes remaining: 0 bytes total: 1099511627776 bytes progression: 100.00 %
transferred: 1099511627776 bytes remaining: 0 bytes total: 1099511627776 bytes progression: 100.00 %
can't deactivate LV '/dev/san3/vm-130-disk-1': Logical volume san3/vm-130-disk-1 in use.
Logical volume "vm-130-disk-1" successfully removed
Logical volume "vm-130-disk-0" successfully removed
import failed - volume deactivation failed: san3:vm-130-disk-1 at /usr/share/perl5/PVE/Storage.pm line 1152.After failing everything is deleted. I also tried importing only the disks to a preconfigured VM, which worked for the first disk, but not for the second big one.
I migrated around 15 similar VMs (two disks) and have only seen this problem once, where a second try with another VM-ID solved the issue. This did not work for this VM.
I searched the forum and found an older issue pointing to pvs/lvs being wrongly active, but this doesn't seem to be the case here:
Code:
~# pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/san3 san3 lvm2 a-- 12.72t <5.93t
/dev/sda3 pve lvm2 a-- <744.68g 15.99g
Code:
~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 4 0 wz--n- <744.68g 15.99g
san3 1 34 0 wz--n- 12.72t <5.93t
Code:
~# lvs -a
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotz-- 612.18g 2.02 0.39
[data_tdata] pve Twi-ao---- 612.18g
[data_tmeta] pve ewi-ao---- 6.25g
[lvol0_pmspare] pve ewi------- 6.25g
root pve -wi-ao---- 96.00g
swap pve -wi-ao---- 8.00g
vm-101-disk-0 pve Vwi-aotz-- 32.00g data 38.72
vm-100-disk-0 san3 -wi-a----- 50.00g
vm-102-disk-0 san3 -wi-ao---- 32.00g
vm-103-disk-0 san3 -wi-a----- 200.00g
vm-103-disk-1 san3 -wi-a----- 100.00g
vm-103-disk-2 san3 -wi-a----- 35.00g
vm-103-disk-3 san3 -wi-a----- 50.00g
vm-103-disk-4 san3 -wi-a----- 50.00g
vm-104-disk-0 san3 -wi-a----- 50.00g
vm-105-disk-0 san3 -wi-a----- 1.00t
vm-106-disk-0 san3 -wi-a----- 256.00g
vm-107-disk-0 san3 -wi-a----- 10.00g
vm-108-disk-0 san3 -wi-ao---- 20.00g
vm-109-disk-0 san3 -wi-ao---- 32.00g
vm-110-disk-0 san3 -wi-a----- 8.00g
vm-111-disk-0 san3 -wi-a----- 50.00g
vm-112-disk-0 san3 -wi-ao---- 50.00g
vm-113-disk-0 san3 -wi-ao---- 20.00g
vm-114-disk-0 san3 -wi-ao---- 16.00g
vm-115-disk-0 san3 -wi-ao---- 50.00g
vm-116-disk-0 san3 -wi-ao---- 20.00g
vm-117-disk-0 san3 -wi-ao---- 500.00g
vm-118-disk-0 san3 -wi-ao---- 100.00g
vm-119-disk-0 san3 -wi-ao---- 20.00g
vm-120-disk-0 san3 -wi-a----- 20.00g
vm-121-disk-0 san3 -wi-a----- 930.50g
vm-121-disk-1 san3 -wi-a----- 1.00g
vm-122-disk-0 san3 -wi-ao---- 20.00g
vm-122-disk-1 san3 -wi-ao---- 50.00g
vm-123-disk-0 san3 -wi-a----- 50.00g
vm-124-disk-0 san3 -wi-ao---- 30.00g
vm-124-disk-1 san3 -wi-ao---- 2.00t
vm-125-disk-0 san3 -wi------- 20.00g
vm-126-disk-0 san3 -wi------- 20.00g
vm-126-disk-1 san3 -wi------- 1.00tVersion Info:
Code:
Kernel Version
Linux 5.4.73-1-pve #1 SMP PVE 5.4.73-1 (Mon, 16 Nov 2020 10:52:16 +0100)
PVE Manager Version
pve-manager/6.3-2/22f57405The import runs from an SSHFS mount onto a FibreChannel attached SAN storage.
