Started getting warning/error messages after upgrade of syncoid

OpenZFS Sanoid
1

Hi,

I have been using the following mechanism for syncing snapshots for a few months now:

#!/usr/local/bin/bash

DATASET_ARRAY=(
	"zroot/data/mysql"
	"zroot/data/var"
	"zroot/data/home/root"
	"zroot/ROOT/default"
)

if ping -c 1 123.456.789.123 &> /dev/null
then
	for DATASET_NAME in "${DATASET_ARRAY[@]}"; do
		syncoid --quiet --preserve-recordsize --preserve-properties --recvoptions="u" --no-privilege-elevation --no-sync-snap --create-bookmark root@123.456.789.123:${DATASET_NAME} storage0/syncoid/laptop/${DATASET_NAME}
	done
fi

Last week I upgrade the sanoid package in FreeBSD from sanoid-2.2.0 to sanoid-2.3.0 – after that I have started getting this:

cannot receive recordsize property on storage0/syncoid/laptop/zroot/data/mysql: permission denied
cannot receive logbias property on storage0/syncoid/laptop/zroot/data/mysql: permission denied
cannot receive primarycache property on storage0/syncoid/laptop/zroot/data/mysql: permission denied
cannot receive recordsize property on storage0/syncoid/laptop/zroot/data/mysql: permission denied
cannot receive logbias property on storage0/syncoid/laptop/zroot/data/mysql: permission denied
cannot receive primarycache property on storage0/syncoid/laptop/zroot/data/mysql: permission denied
cannot receive canmount property on storage0/syncoid/laptop/zroot/data/var: permission denied
CRIT: --no-sync-snap is set, and getnewestsnapshot() could not find any snapshots on source!
CRITICAL ERROR:
Target storage0/syncoid/laptop/zroot/ROOT/default exists but has no snapshots matching with zroot/ROOT/default!
Replication to target would require destroying existing
target. Cowardly refusing to destroy your existing target.

Any clue to why this might have changed?

What could I do to not get these warning messages?

Thanks in advance!

2

This is the part you need to troubleshoot. Are there, in fact, no snapshots present on the source?

It also makes life more difficult that we’re seeing errors from a loop of syncoid runs; it’s not clear whether all these errors are valid individual errors, or one error causing a bunch of misreported stuff.

If the “permission denied” errors about preserving properties are valid in their own right (not simply wharrgarbl caused by the “no snapshots found” error), you most likely have implemented ZFS delegation to replicate as a non-root user, and have not correctly delegated all the permissions necessary to use --preserve-properties on the target side.

3

Thanks for your reply!

Yes, I have delegated zfs permissions do an user called: syncoid.

This is how the permissions looks:

user syncoid bookmark,compression,create,destroy,hold,mount,mountpoint,receive,recordsize,rollback,send,snapshot

Am I missing anything there?

Regarding the snapshots – these error message seem to be a combination between me adding more datasets to be backed up and a few weeks of no contact between backup server and source – these messages are now gone.