Offline migration fails

term

Well-Known Member
Aug 29, 2013
71
1
48
Offline migration fails for me when I try to move from a newer proxmox 4 install that has been upgraded to 5.1, to a older proxmox 5.1 install that started with proxmox 3.

The storage involved is not marked shared, but the older server has local storage configured as true plain local storage, where pve data is just ext3 assigned to a folder.

The new server is using lvm-thin storage for its local storage.

What should I do to make this workable? Create lvm-thin storage on the older servers? If so, how?

Code:
2018-01-03 09:34:05 starting migration of VM 504 to node 'px4' (10.0.0.22)
2018-01-03 09:34:05 found local disk 'local-lvm:vm-504-disk-1' (in current VM config)
2018-01-03 09:34:05 copying disk images
lvcreate 'pve/vm-504-disk-1' error:   Logical volume pve/data is not a thin pool.
dd: error writing 'standard output': Connection reset by peer
54+0 records in
53+0 records out
3536424 bytes (3.5 MB, 3.4 MiB) copied, 0.212909 s, 16.6 MB/s
exit code 255
command 'dd 'if=/dev/pve/vm-504-disk-1' 'bs=64k'' failed: exit code 1
send/receive failed, cleaning up snapshot(s)..
2018-01-03 09:34:06 ERROR: Failed to sync data - command 'set -o pipefail && pvesm export local-lvm:vm-504-disk-1 raw+size - -with-snapshots 0' failed: exit code 1
2018-01-03 09:34:06 aborting phase 1 - cleanup resources
2018-01-03 09:34:06 ERROR: found stale volume copy 'local-lvm:vm-504-disk-1' on node 'px4'
2018-01-03 09:34:06 ERROR: migration aborted (duration 00:00:01): Failed to sync data - command 'set -o pipefail && pvesm export local-lvm:vm-504-disk-1 raw+size - -with-snapshots 0' failed: exit code 1
TASK ERROR: migration aborted
 
did you restrict 'local-lvm' to the one where it exists? if not, pve assumes it is available on all nodes

since you have a lv named 'data' on both nodes, i guess it will not be possible to use migration between those nodes using 'local-lvm'

a solution would be to create a new thin pool on both (named the same) and use that
 
edit: /etc/pve/storage.cfg

Code:
lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images
        nodes px3,px4
dir: local
        path /var/lib/vz
        content images,iso,backup,rootdir,vztmpl
        maxfiles 0
        nodes px2

I thought this was going to work, but now when I try to do a offline migration, it tells me that local-lvm does not exist on the other node. Does it always have to migrate to the exact same storage type?
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!