On 08/23/2017 08:50 PM, Gilberto Nunes wrote:
more info:
pvesr status
JobID Enabled Target LastSync
NextSync Duration FailCount State
100-0 Yes local/prox01 -
2017-08-23_15:55:04 3.151884 1 command 'set -o pipefail &&
pvesm export local-zfs:vm-100-disk-1 zfs - -with-snapshots 1 -snapshot
__replicate_100-0_1503514204__ | /usr/bin/cstream -t 1024000000 |
/usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=prox01' root@10.1.1.10 --
pvesm import local-zfs:vm-100-disk-1 zfs - -with-snapshots 1' failed: exit
code 255
100-1 Yes local/prox02 -
2017-08-23_15:55:01 3.089044 1 command 'set -o pipefail &&
pvesm export local-zfs:vm-100-disk-1 zfs - -with-snapshots 1 -snapshot
__replicate_100-1_1503514201__ | /usr/bin/cstream -t 1024000000 |
/usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=prox02' root@10.1.1.20 --
pvesm import local-zfs:vm-100-disk-1 zfs - -with-snapshots 1' failed: exit
code 255
according to this output, no lastsync was completed, so i guess the
replication did never work, so the migration will also not worK?
i would remove all replication jobs (maybe with -force, via commandline)
delete all images of this vm from all nodes where the vm *not* is at the
moment (afaics from prox01 and prox02, as the vm is currently on prox03)
then add the replication again wait for it to complete (verify with
pvesr status) and try again to migrate
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
