Error restoring vzdump from PVE-2.3 on PVE-3.1

[orangelemon]

I have an vzdump from an openvz container made on PVE 2.3, and trying to restore it on 3.1 but it throws this error:

Starting container ...
mount: special device /www/101 does not exist
Error executing mount script /etc/pve/openvz/103.mount
TASK ERROR: command 'vzctl start 103' failed: exit code 79

This containter originates from a 1.9 cluster....

Anyone any ideas?

pveversion -v

root@srv2:~# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2

 

[orangelemon]

What is the logic in this?

SRC=/www/101
DST=/www

And why does the other VM (101) have no /etc/pve/openvz/101.mount

Is this a legacy issue?

 

[orangelemon]

Ok... writing stuff here makes things more clearly appently

I've removed the 103.mount file and nog it appears to work...

Can anyone from the proxmox team confirm that this is the right way? Or did I just broke it at another place without noticing it (yet)