pve-zsync failes on restored lxc

J

Jero

Member
May 20, 2016
33
2
8
44
Hi Guys,
First let me thank you with this fantastic pace of software!

I am testing the pve-zsync between two pve hosts, no problem between fresh installed lxc containers but when i delete a container and restore a backup the zsync does not work anymore:

Working / fresh container:
Code: 
root@pve-backup:/etc/pve/lxc# pve-zsync sync --source 102 --dest 192.168.1.91:evopool/backup --verbose --maxsnap 1 --name testsync
send from @ to rpool/data/subvol-102-disk-1@rep_testsync_2016-05-20_11:14:55 estimated size is 2.49G
total estimated size is 2.49G
TIME        SENT   SNAPSHOT
11:14:57    104M   rpool/data/subvol-102-disk-1@rep_testsync_2016-05-20_11:14:55
11:14:58    205M   rpool/data/subvol-102-disk-1@rep_testsync_2016-05-20_11:14:55
....
11:15:21   2.55G   rpool/data/subvol-102-disk-1@rep_testsync_2016-05-20_11:14:55
Not working / after restore backup:
Code: 
root@pve-backup:/etc/pve/lxc# pve-zsync sync --source 102 --dest 192.168.1.91:evopool/backup --verbose --maxsnap 1 --name testsync
COMMAND:
   pvesm path 'volume=local-zfs:subvol-102-disk-1'
GET ERROR:
   400 Parameter verification failed.
volume: invalid format - unable to parse volume ID 'volume=local-zfs:subvol-102-disk-1'

pvesm path <volume>


zfs list source:
Code: 
rpool/ROOT                    2.88G  43.8G    96K  /rpool/ROOT
rpool/ROOT/pve-1              2.88G  43.8G  2.77G  /
rpool/data                    6.66G  43.8G    96K  /rpool/data
rpool/data/subvol-101-disk-1   427M  7.58G   427M  /rpool/data/subvol-101-disk-1
rpool/data/subvol-102-disk-1  1.66G  10.3G  1.66G  /rpool/data/subvol-102-disk-1
rpool/data/vm-100-disk-1       669M  43.8G   666M  -
rpool/data/vm-103-disk-1      3.93G  43.8G  3.93G  -
rpool/swap                    4.25G  48.0G  80.7M  -

I know that zsync is in development, just not sure if it is a user error...

Greetz
 
Last edited:
Removing "volume=" from /etc/pve/lxc/100.conf solves the pve-zsync create problem.

from:
rootfs: volume=local-zfs:subvol-100-disk-1,size=4G

to:
rootfs: local-zfs:subvol-100-disk-1,size=4G
 
  • Like
Reactions: BuffaloBrent
I can replicate this issue as well.

hammurabi's solution works for me, although the .conf file was located in a different location, and I had to remove "file=" instead, but it worked to correct the issue just the same.

The more I use this pve-zsync function, the more I'm impressed with it! Hopefully small items about it will be fix/added to in future releases, but they're nothing that I can't handle.
 
You must log in or register to reply here.
Top Bottom