{"action":"created","issue":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4050","labels_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4050/labels{/name}","comments_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4050/comments","events_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4050/events","html_url":"https://github.com/zfsonlinux/zfs/issues/4050","id":119102415,"number":4050,"title":"Incremental zfs send does not transmit hole","user":{"login":"Ringdingcoder","id":173088,"avatar_url":"https://avatars.githubusercontent.com/u/173088?v=3","gravatar_id":"","url":"https://api.github.com/users/Ringdingcoder","html_url":"https://github.com/Ringdingcoder","followers_url":"https://api.github.com/users/Ringdingcoder/followers","following_url":"https://api.github.com/users/Ringdingcoder/following{/other_user}","gists_url":"https://api.github.com/users/Ringdingcoder/gists{/gist_id}","starred_url":"https://api.github.com/users/Ringdingcoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ringdingcoder/subscriptions","organizations_url":"https://api.github.com/users/Ringdingcoder/orgs","repos_url":"https://api.github.com/users/Ringdingcoder/repos","events_url":"https://api.github.com/users/Ringdingcoder/events{/privacy}","received_events_url":"https://api.github.com/users/Ringdingcoder/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-26T21:11:02Z","updated_at":"2015-11-30T19:58:09Z","closed_at":null,"body":"Apparently, there are various related bug reports floating around, but AFAICT they all concern the @hole_birth feature. I have a case that seems very similar, but without having ever touched @hole_birth. The symptom is that on the receiving clone, some holes get filled with semi-random data.\r\n\r\nDetails on the mailing list:\r\nhttp://list.zfsonlinux.org/pipermail/zfs-discuss/2015-November/023899.html\r\nand\r\nhttp://list.zfsonlinux.org/pipermail/zfs-discuss/2015-November/023909.html (self-reply to previous mail)\r\n\r\nI've also tested this with the patch from openzfs/openzfs#37 applied, but this does not make the least bit of a difference."},"comment":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/comments/160741253","html_url":"https://github.com/zfsonlinux/zfs/issues/4050#issuecomment-160741253","issue_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4050","id":160741253,"user":{"login":"Ringdingcoder","id":173088,"avatar_url":"https://avatars.githubusercontent.com/u/173088?v=3","gravatar_id":"","url":"https://api.github.com/users/Ringdingcoder","html_url":"https://github.com/Ringdingcoder","followers_url":"https://api.github.com/users/Ringdingcoder/followers","following_url":"https://api.github.com/users/Ringdingcoder/following{/other_user}","gists_url":"https://api.github.com/users/Ringdingcoder/gists{/gist_id}","starred_url":"https://api.github.com/users/Ringdingcoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ringdingcoder/subscriptions","organizations_url":"https://api.github.com/users/Ringdingcoder/orgs","repos_url":"https://api.github.com/users/Ringdingcoder/repos","events_url":"https://api.github.com/users/Ringdingcoder/events{/privacy}","received_events_url":"https://api.github.com/users/Ringdingcoder/received_events","type":"User","site_admin":false},"created_at":"2015-11-30T19:58:08Z","updated_at":"2015-11-30T19:58:08Z","body":"Yes, it does. Given that it happens with Illumos as well, I wouldn’t have expected anything else. It seems like this bug has been there \"forever\" (probably only since version 5000)."}}