{"action":"created","issue":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4287","repository_url":"https://api.github.com/repos/zfsonlinux/zfs","labels_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4287/labels{/name}","comments_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4287/comments","events_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4287/events","html_url":"https://github.com/zfsonlinux/zfs/issues/4287","id":129840596,"number":4287,"title":"zfs get behavior changed at sys-fs/zfs-0.6.5.4-r2","user":{"login":"AndCycle","id":4460370,"avatar_url":"https://avatars.githubusercontent.com/u/4460370?v=3","gravatar_id":"","url":"https://api.github.com/users/AndCycle","html_url":"https://github.com/AndCycle","followers_url":"https://api.github.com/users/AndCycle/followers","following_url":"https://api.github.com/users/AndCycle/following{/other_user}","gists_url":"https://api.github.com/users/AndCycle/gists{/gist_id}","starred_url":"https://api.github.com/users/AndCycle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AndCycle/subscriptions","organizations_url":"https://api.github.com/users/AndCycle/orgs","repos_url":"https://api.github.com/users/AndCycle/repos","events_url":"https://api.github.com/users/AndCycle/events{/privacy}","received_events_url":"https://api.github.com/users/AndCycle/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2016-01-29T18:04:00Z","updated_at":"2016-02-17T14:38:20Z","closed_at":null,"body":"@ryao \r\n\r\nI hit this because zrep heavily rely on zfs properties,\r\n\r\nhere is the example code which should show the snap\r\n```\r\n$ zfs create pool/test\r\n$ zfs snapshot pool/test@snap\r\n$ zfs set zrep:sent=123456 pool/test@snap\r\n$ zfs get -H -o name -r -s local zrep:sent pool/test\r\npool/test@snap\r\n```\r\n\r\nat sys-fs/zfs-0.6.5.4-r2,\r\nthe zfs get return nothing\r\n```\r\n$ zfs create pool/test\r\n$ zfs snapshot pool/test@snap\r\n$ zfs set zrep:sent=123456 pool/test@snap\r\n$ zfs get -H -o name -r -s local zrep:sent pool/test\r\n```"},"comment":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/comments/185232237","html_url":"https://github.com/zfsonlinux/zfs/issues/4287#issuecomment-185232237","issue_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4287","id":185232237,"user":{"login":"ryao","id":1386373,"avatar_url":"https://avatars.githubusercontent.com/u/1386373?v=3","gravatar_id":"","url":"https://api.github.com/users/ryao","html_url":"https://github.com/ryao","followers_url":"https://api.github.com/users/ryao/followers","following_url":"https://api.github.com/users/ryao/following{/other_user}","gists_url":"https://api.github.com/users/ryao/gists{/gist_id}","starred_url":"https://api.github.com/users/ryao/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ryao/subscriptions","organizations_url":"https://api.github.com/users/ryao/orgs","repos_url":"https://api.github.com/users/ryao/repos","events_url":"https://api.github.com/users/ryao/events{/privacy}","received_events_url":"https://api.github.com/users/ryao/received_events","type":"User","site_admin":false},"created_at":"2016-02-17T14:38:20Z","updated_at":"2016-02-17T14:38:20Z","body":"\n> On Feb 17, 2016, at 2:40 AM, ilovezfs <notifications@github.com> wrote:\n> \n> @AndCycle Unless you have 10 levels of descendents, zfs list -d 10 -t snapshot zbackup-20150922 should not list anything at all.\n> \n> @ryao That is not correct.\n> \n> illumos:\n> \n> root@omni151017:/root# zfs list -d 10 -t snapshot rpool\n> NAME                        USED  AVAIL  REFER  MOUNTPOINT\n> rpool/ROOT/omnios@install   273M      -  1.62G  \n> Which is exactly what you'd expect based on what the man page says.\n> \n> As for -r and -d, since they are explicitly defined as mutually exclusive in the man page, using them in combination has undefined behavior unless the man page were to also specify what the combined behavior should be. illumos does the following:\n> \n> root@omni151017:/root# zfs list -r -d 0 rpool\n> NAME    USED  AVAIL  REFER  MOUNTPOINT\n> rpool  3.93G  11.4G    22K  /rpool\n> root@omni151017:/root# zfs list -d 0 rpool\n> NAME    USED  AVAIL  REFER  MOUNTPOINT\n> rpool  3.93G  11.4G    22K  /rpool\n> root@omni151017:/root#\n> which is the same behavior @AndCycle says ZoL master has. By contrast the stable API treats zfs list -d 0 -r o3xpool and zfs list -r o3xpool identically ignoring -d entirely.\n> \n\nThanks for the correction. I forgot that -D was maximum depth rather than minimum depth. The latter of which is not present in the original code. I will put this in my queue to check after the other regression fixes are ready.\n> —\n> Reply to this email directly or view it on GitHub.\n> \n"}}