target exists but has no matching snapshots! about sanoid HOT 8 CLOSED

Please try your sync with the --debug flag, and post the output here.

Example: syncoid pool/dataset pool/otherdataset --debug

from sanoid.

Any update, @0xFate ?

from sanoid.

sorry i actually encounterd that while in an reabuild process so i had to focus on my servers first before debugging it. i found old syncoid snapshots wich may have caused that problem. ill come back on that later when finished and cleaned up messy snapshots

from sanoid.

Yeah indeed it was the messy snapshots after an cleanup it worked lik a charm again. i may spend some time in writing some exception handling for that this weekend.

from sanoid.

Don't know if you noticed, btw, but a lot of that new code I added was adding sudo support to syncoid. It will now automatically detect if it should use sudo (example syncoid syncoid@remotebox:pool/dataset localpool/dataset), so as long as the user on the remote end has NOPASSWD available for /sbin/zfs, everything works great.

from sanoid.

yeah thats why o opened this in the first place b/c i supposed that changes to be the issue in some way but i read the code and it rules out sudo when @root.

from sanoid.

Yup. Coming up pretty soon on the roadmap will be the ability to communicate directly with a remote sanoid, to minimize the SSH traffic and also the amount of privilege needed to grant to a remote machine. IE have a wrapper syncoid-send that calls syncoid --send [arguments], which can obligingly cough up all of the necessary information about snapshots and capabilities in one go, can be given privileges to handle only certain datasets but not others, etc.

from sanoid.

great to hear that, i already wrapped my head around that a bit either. when you want to do the caching of snap/vol list on FS please consider a cfg file and an option to set cache dir and sync data source. that way you could easily adapt caching on clusterFS (glusterfs,ocfs) for accessing remote cache directly, or ramdisk for faster access.
if you go upstream w/ the feature you planned ill definitivly spaer some time in working on that :)

from sanoid.