pve-zsync disk has no valid zfs dataset format and will be skipped

Richard Isted

Active Member
Jul 18, 2019
12
0
41
48
Hi Everyone,

I've got Proxmox installed on my home server. I upgraded to version 6 last night and am trying to get pve-zsync configured and running but I had a strange issue.

I have two ZFS pools (vmdata01 and vmdata02), one with 7200rpm drives and the other with SSD drives. On my linux VM I am using 3 SCSI virtual disks, with the boot and swap on the SSD volume (vmdata02) and the data volume on vmdata01.

When I run pve-zsync for the first time when I ran into issues because I two disks with the same name (scsi0: vmdata02:vm-101-disk-0 and scsi4: vmdata:vm-101-disk-0,discard=on,size=300G). I tried renaming the disk residing on the ssd volume using zfs rename to vm-101-disk-0_ssd and vm-101-ssd_disk-0 however when the disk is named any format other than the standard I get the following error:

Disk: "scsi1: vmdata02:vm-102-ssd_disk-0,discard=on,size=4G,ssd=1" has no invalid zfs dataset format and will be skipped

I have managed to work round this issue by naming the disk vm-102-ssd_disk-9 so the last digit does not clash with any other disk in the system. This seems to have allowed me to run a complete pve-zsync.

Just thought I would share.

Would love to see the ability to have daily, weekly and monthly synced snapshots all linked to the same destination zfs share / dataset, so you don't have additional duplication of data. Great tool, thanks.
 
From a zfs point of view, you want to sync a dataset with same name, that's why it is clashing. The naming scheme is key for different operation on Proxmox, best that you just changed the number for it.