{"action":"created","issue":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4898","repository_url":"https://api.github.com/repos/zfsonlinux/zfs","labels_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4898/labels{/name}","comments_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4898/comments","events_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4898/events","html_url":"https://github.com/zfsonlinux/zfs/issues/4898","id":168220288,"number":4898,"title":"Systemd: Replace zfs-mount.service with systemd.generator(7)","user":{"login":"pyropeter","id":96421,"avatar_url":"https://avatars.githubusercontent.com/u/96421?v=3","gravatar_id":"","url":"https://api.github.com/users/pyropeter","html_url":"https://github.com/pyropeter","followers_url":"https://api.github.com/users/pyropeter/followers","following_url":"https://api.github.com/users/pyropeter/following{/other_user}","gists_url":"https://api.github.com/users/pyropeter/gists{/gist_id}","starred_url":"https://api.github.com/users/pyropeter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyropeter/subscriptions","organizations_url":"https://api.github.com/users/pyropeter/orgs","repos_url":"https://api.github.com/users/pyropeter/repos","events_url":"https://api.github.com/users/pyropeter/events{/privacy}","received_events_url":"https://api.github.com/users/pyropeter/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-07-28T23:32:01Z","updated_at":"2016-08-19T14:11:53Z","closed_at":null,"body":"After debugging a new installation with /var in a separate dataset for a day, I'm now under the impression that the current way of mounting zfs datasets on boot is completely broken. Several bug reports in this tracker confirm this (#3768, #4784, #4474, etc...).\r\n\r\nIt seems to me that zfs should follow the normal way of mounting filesystems on systemd (using mount-units that are auto-generated by systemd-fstab-generator). Benefits would be that systemd will ensure that all mounts are done in the correct order (even if zfs- and fstab-mounts are interleaved) and that nothing will write into the empty directories right before mounting.\r\n\r\nTo achive this, one would have to write a systemd.generator(7) that outputs one mount-unit for each dataset that would be mounted by `zfs mount -a`. This generator is run when systemd starts up, so that might be difficult for some reason (I never wrote software for early boot).\r\n\r\nAm I missing something or could that actually work?"},"comment":{"url":"https://api.github.com/repos/zfsonlinux/zfs/issues/comments/241029082","html_url":"https://github.com/zfsonlinux/zfs/issues/4898#issuecomment-241029082","issue_url":"https://api.github.com/repos/zfsonlinux/zfs/issues/4898","id":241029082,"user":{"login":"neurotensin","id":13261196,"avatar_url":"https://avatars.githubusercontent.com/u/13261196?v=3","gravatar_id":"","url":"https://api.github.com/users/neurotensin","html_url":"https://github.com/neurotensin","followers_url":"https://api.github.com/users/neurotensin/followers","following_url":"https://api.github.com/users/neurotensin/following{/other_user}","gists_url":"https://api.github.com/users/neurotensin/gists{/gist_id}","starred_url":"https://api.github.com/users/neurotensin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/neurotensin/subscriptions","organizations_url":"https://api.github.com/users/neurotensin/orgs","repos_url":"https://api.github.com/users/neurotensin/repos","events_url":"https://api.github.com/users/neurotensin/events{/privacy}","received_events_url":"https://api.github.com/users/neurotensin/received_events","type":"User","site_admin":false},"created_at":"2016-08-19T14:11:53Z","updated_at":"2016-08-19T14:11:53Z","body":"As a data point, it is important that users *do not* create their own mount points for zfs. I just diagnosed my own problem with this error , and had forgotten that I created /zfsmount (say) then /zfsmount/stuff . zfs mount -a kept complaining cannot mount '/zfsmount': directory is not empty, which now I understand is correct. \r\n\r\nif you do \"mount |grep zfs\" and see /zfsmount/stuff without /zfsmount on its own, you will get this error. \r\n\r\nzfs creates its own mount points and there should be nothing in fstab to contradict that, until zfs is up and running."}}
{"actor":{"display_login":"neurotensin"}}