Bugs in Disk Move?

[ejc317]

I have a VM ID 100

Disk 1 on SAN is VM-100-Disk-1.
Disk 2 on NFS is VM-100-Disk-1

when you mvoe the name overlaps. Shouldn't that second disk be VM-100-Disk-1 when you move or when it's just sitting there?

 

[spirit]

when you move a disk to a target storage, proxmox will try to find the next free volume id.

so, in your example,

if you move disk1 to NFS, the new volume name will be vm-100-disk-2

 

[ejc317]

when you move a disk to a target storage, proxmox will try to find the next free volume id.

so, in your example,

if you move disk1 to NFS, the new volume name will be vm-100-disk-2

TASK ERROR: storage migration failed: mirroring error: error job is not mirroring at /usr/share/perl5/PVE/QemuServer.pm line 4691.

I got that - and if I change disk to vm-100-disk-2 it works

 

[ejc317]

TASK ERROR: storage migration failed: mirroring error: error job is not mirroring at /usr/share/perl5/PVE/QemuServer.pm line 4691.

I got that - and if I change disk to vm-100-disk-2 it works

The disk couldnt move and then it corrupted the lv ... i had to restore from a 24 hour backup - customer is not happy ... this should be looked into guys