Out of space pve-zsync

Rubicon

New Member
Apr 17, 2017
7
0
1
46
Hello.

root@samba:~# pve-zsync sync --source 100 --dest 10.1.1.207:tankb/Weekly --verbose --maxsnap 3 --name pve-weekly-samba
WARN: COMMAND:
zfs destroy tank/vm-100-disk-1@rep_pve-weekly-samba_2017-05-12_13:00:09
GET ERROR:
could not find any snapshots to destroy; check snapshot names.
WARN: COMMAND:
ssh root@10.1.1.207 -- zfs destroy tankb/Weekly/vm-100-disk-1@rep_pve-weekly-samba_2017-05-12_13:00:09
GET ERROR:
cannot open 'tankb/Weekly/vm-100-disk-1': dataset does not exist
Job --source 100 --name pve-weekly-samba got an ERROR!!!
ERROR Message:
COMMAND:
zfs snapshot tank/vm-100-disk-1@rep_pve-weekly-samba_2017-05-12_13:00:09
GET ERROR:
cannot create snapshot 'tank/vm-100-disk-1@rep_pve-weekly-samba_2017-05-12_13:00:09': out of space


It turns out that he creates a local snapshot first, and only then he sends it to a remote computer?
I created a pool for the entire disk, what should I recreate it for, so that zpool would take up less space?
I thought he was sending a snapshot over the network right away.


root@samba:~# zfs list -o name,quota,refquota,reservation,refreservation
NAME QUOTA REFQUOTA RESERV REFRESERV
rpool none none none none
rpool/ROOT none none none none
rpool/ROOT/pve-1 none none none none
rpool/data none none none none
rpool/swap - - none 8.50G
tank none none none none
tank/vm-100-disk-1 - - none 3.51T
 
Hi,

You have to be space on the pool to create a snapshot.
So if you make a zvol with the same size as the pool is the pve-zsync will not work.
 
  • Like
Reactions: Rubicon
Hi,

You have to be space on the pool to create a snapshot.
So if you make a zvol with the same size as the pool is the pve-zsync will not work.

I have 2 disks of 4 TB each, how do I make the system the first disk, and the snapshot on the second disk? Is this possible?
 
Or is it easier for me to mount secondary disk into a directory and select it as a repository a backup storage?

root@samba:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 10.5G 97.1G 96K /rpool
rpool/ROOT 1.95G 97.1G 96K /rpool/ROOT
rpool/ROOT/pve-1 1.95G 97.1G 1.95G /
rpool/data 96K 97.1G 96K /rpool/data
rpool/swap 8.50G 106G 64K -
tank 3.51T 6.39G 96K /tank
tank/vm-100-disk-1 3.51T 3.45T 60.7G -

Maybe I created the pool incorrectly?
 
Last edited:
restore vma archive: vma extract -v -r /var/tmp/vzdumptmp23300.fifo /mnt/pve/nfs/dump/vzdump-qemu-100-2017_05_12-16_47_27.vma /var/tmp/vzdumptmp23300

I restore the backup copy. It turns out he still extracts the archive, even if compression is not selected? Where does he extract it?