Comment 4 for bug 1835697

A workaround to get the dependencies installed on upgrade would be:

$ sudo systemctl mask zfs-mount
$ sudo apt -f install
$ sudo systemctl unmask zfs-mount

After a reboot the ``zfs-mount`` service stays in a failed state, I wonder if something else has taken on its duties and there is a conflict when in a ZFS-on-root scenario?

My ZFS filesystems are definitely mounted, live and kicking

$ sudo systemctl status zfs-mount
● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-09-06 06:17:35 CEST; 3min 28s ago
     Docs: man:zfs(8)
  Process: 2995 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
 Main PID: 2995 (code=exited, status=1/FAILURE)

Sep 06 06:17:35 frode-Precision-7530 systemd[1]: Starting Mount ZFS filesystems...
Sep 06 06:17:35 frode-Precision-7530 zfs[2995]: cannot mount '/root': directory is not empty
Sep 06 06:17:35 frode-Precision-7530 zfs[2995]: cannot mount '/var/lib': directory is not empty
Sep 06 06:17:35 frode-Precision-7530 systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE
Sep 06 06:17:35 frode-Precision-7530 systemd[1]: zfs-mount.service: Failed with result 'exit-code'.
Sep 06 06:17:35 frode-Precision-7530 systemd[1]: Failed to start Mount ZFS filesystems.