Comment 15 for bug 1922293

[from-irc]
<didrocks> mvo: hey! There are 2 things here:
<didrocks> - the zfs generator is currently broken in the default setup due to OpenZFS 2.0 default layout. ubiquity in unapproved since this morning is fixing this
<didrocks> (people using our default setup will not be impacted by the bug then)
<didrocks> - then, for people using ZFS themselves (no ZSys/not our default setup with a generator), indeed, all the .mount units needs to specify After=zfs-mount.service as
<didrocks> Pawel suggested
<didrocks> (as the mount points are only available once zfs-mount.service has run)
<didrocks> mvo: I guess cking (who is our ZFS maintainer) can have a second eye on this, but the truth shouldn’t be far from that :)
<mvo> didrocks: cool, thanks. so your recommendation is that we implement the workaround?
<mvo> didrocks: for those who use non-defaults?
<didrocks> mvo: correct, for everyone using non default having a dataset as a parent directory where you mount the snaps (for the .mount files)