{"action":"created","issue":{"url":"https://api.github.com/repos/jimsalterjrs/sanoid/issues/46","repository_url":"https://api.github.com/repos/jimsalterjrs/sanoid","labels_url":"https://api.github.com/repos/jimsalterjrs/sanoid/issues/46/labels{/name}","comments_url":"https://api.github.com/repos/jimsalterjrs/sanoid/issues/46/comments","events_url":"https://api.github.com/repos/jimsalterjrs/sanoid/issues/46/events","html_url":"https://github.com/jimsalterjrs/sanoid/issues/46","id":171944449,"number":46,"title":"Syncoid cannot receive incremental stream: most recent snapshot does not match incremental source","user":{"login":"asmartin","id":3905723,"avatar_url":"https://avatars.githubusercontent.com/u/3905723?v=3","gravatar_id":"","url":"https://api.github.com/users/asmartin","html_url":"https://github.com/asmartin","followers_url":"https://api.github.com/users/asmartin/followers","following_url":"https://api.github.com/users/asmartin/following{/other_user}","gists_url":"https://api.github.com/users/asmartin/gists{/gist_id}","starred_url":"https://api.github.com/users/asmartin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/asmartin/subscriptions","organizations_url":"https://api.github.com/users/asmartin/orgs","repos_url":"https://api.github.com/users/asmartin/repos","events_url":"https://api.github.com/users/asmartin/events{/privacy}","received_events_url":"https://api.github.com/users/asmartin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-08-18T16:28:44Z","updated_at":"2016-08-18T17:29:31Z","closed_at":null,"body":"I recently configured sanoid and syncoid on Ubuntu 16.04 to take snapshots on `host1` and sync them to `host2`. This appeared to work well at first, but eventually syncoid fails out with this error:\r\n\r\n````\r\nroot@host1 # syncoid -r pool/dataset1 root@host2:pool/dataset1\r\nSending incremental pool/dataset1@syncoid_host1_2016-08-18:11:00:12 ... syncoid_host1_2016-08-18:11:07:58 (~ 4 KB):\r\nSending incremental pool/dataset1/data@autosnap_2016-08-18_11:00:01_hourly ... syncoid_host1_2016-08-18:11:07:59 (~ 4 KB):\r\ncannot receive incremental stream: most recent snapshot of pool/dataset1/data does not\r\nmatch incremental source\r\nCRITICAL ERROR:  /sbin/zfs send -I pool/dataset1/data@autosnap_2016-08-18_11:00:01_hourly pool/dataset1/data@syncoid_host1_2016-08-18:11:07:59 | /usr/bin/pv -s 4096 | /usr/bin/lzop  | /usr/bin/mbuffer  -q -s 128k -m 16M 2>/dev/null | /usr/bin/ssh -c chacha20-poly1305@openssh.com,arcfour -p 22 -S /tmp/syncoid-root-root@host2-1471536477 root@host2 ' /usr/bin/mbuffer  -q -s 128k -m 16M 2>/dev/null | /usr/bin/lzop -dfc |  /sbin/zfs receive pool/dataset1/data' failed: 256 at /usr/local/bin/syncoid line 241.\r\n````\r\n\r\nAccording to [the Oracle documentation](https://docs.oracle.com/cd/E26505_01/html/E37384/gbchx.html), this error occurs if the data related to the dataset is modified on the destination (`host2`), however if I run `zfs get mounted pool/dataset1/data` on `host2` it shows that it is not mounted, thus it seems unlikely that the data was modified on `host2`. I do see that `atime` is on, but again how does that matter since it isn't mounted. What do I need to do to resolve this error?\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/jimsalterjrs/sanoid/issues/comments/240796254","html_url":"https://github.com/jimsalterjrs/sanoid/issues/46#issuecomment-240796254","issue_url":"https://api.github.com/repos/jimsalterjrs/sanoid/issues/46","id":240796254,"user":{"login":"jimsalterjrs","id":1280796,"avatar_url":"https://avatars.githubusercontent.com/u/1280796?v=3","gravatar_id":"","url":"https://api.github.com/users/jimsalterjrs","html_url":"https://github.com/jimsalterjrs","followers_url":"https://api.github.com/users/jimsalterjrs/followers","following_url":"https://api.github.com/users/jimsalterjrs/following{/other_user}","gists_url":"https://api.github.com/users/jimsalterjrs/gists{/gist_id}","starred_url":"https://api.github.com/users/jimsalterjrs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimsalterjrs/subscriptions","organizations_url":"https://api.github.com/users/jimsalterjrs/orgs","repos_url":"https://api.github.com/users/jimsalterjrs/repos","events_url":"https://api.github.com/users/jimsalterjrs/events{/privacy}","received_events_url":"https://api.github.com/users/jimsalterjrs/received_events","type":"User","site_admin":false},"created_at":"2016-08-18T17:29:31Z","updated_at":"2016-08-18T17:29:31Z","body":"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."}}
{"actor":{"display_login":"jimsalterjrs"}}