-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syncoid cannot receive incremental stream: most recent snapshot does not match incremental source #46
Comments
You're almost certainly taking snapshots on the target side, and ending up with target snapshots taken locally which have the same names as source snapshots. This will especially happen if you run Sanoid with "production" templates on the target side as well as the source side. If you run Sanoid on the target, you need to use the "backup" template (or just make sure autosnap is set to false) - new snapshots are supposed to replicate in from source, not be taken locally. |
Thanks for the quick response! Here is the setup I have host1:
host2:
I have sanoid configured as follows on host1:
and on host2:
Do I have something wrong with the logic in the sanoid config files? Sanoid on |
Something has taken a snapshot with the same name but different content on host2 than on host1, be it Sanoid - with or without an earlier configuration that doesn't match the one shown here - or something else. The error message you've given here - "most recent snapshot does not match incremental source" - can't be thrown any other way, that I'm aware of. Keep in mind also that Syncoid uses the -F argument for its |
Do you have any snapshots on host2 that are not created by Sanoid or Syncoid? You've sanitized your hostnames here - do you have multiple hosts with the same actual hostname? (Keep in mind that Syncoid creates its own sync snapshots using the hostname, meaning that if you have multiple machines with the same hostname, you can create some collisions between syncoid snapshots.) |
I am only creating snapshots with sanoid and checked |
Honestly the -F shouldn't matter, because syncoid itself already forcibly rolls back the target prior to replication. That said, ANYTHING in Master on GitHub in my repo is something I consider "production ready" - if it's still in testing, I don't push to master, I either keep it local or fork a dev branch off. And yes, I'd give 1.4.7 a shot. |
Testing with 1.4.7 is working so far. I will keep testing for another day or two before considering this fixed. Can you tag 1.4.7 so I can download it directly rather than pulling from master? |
Running with 1.4.7 has been working for several days, I think this is the solution. Thanks for the help! |
I recently configured sanoid and syncoid on Ubuntu 16.04 to take snapshots on
host1
and sync them tohost2
. This appeared to work well at first, but eventually syncoid fails out with this error:According to the Oracle documentation, this error occurs if the data related to the dataset is modified on the destination (
host2
), however if I runzfs get mounted pool/dataset1/data
onhost2
it shows that it is not mounted, thus it seems unlikely that the data was modified onhost2
. I do see thatatime
is on, but again how does that matter since it isn't mounted. What do I need to do to resolve this error?Thanks!
The text was updated successfully, but these errors were encountered: