Open smammy opened 8 years ago
@smammy,
This is a known corner case for mountall
, and one of the reasons why it was deprecated in Ubuntu for the systemd stack.
Two potential solutions are:
mountpoint=/srv/nfs4/data
on the dataset and bind it back to /storage/data
in the /fstab.)upstart
job that listens for the MOUNTED=/storage/data
event and depends on the NFS service.Past that, if you're building a new system and need this kind of configuration, then think about using Xenial.
I am using the stable ZFS PPA. On my system,
fstab
entries that bind mount ZFS filesystems to directories on my (non-ZFS) root filesystem causemountall
to fail to mount any ZFS filesystems.When I boot,
/storage
doesn't get mounted, andmountall
complains about not being able to mount/srv/nfs4/data
. Here is the output ofmountall --debug
(with Plymouth connection warnings removed):try_mount
has somehow gotten the idea thatstorage
(the ZFS base filesystem) depends on/srv/nfs4/data
, which in reality a bind mount target:And then a little later on, it tries to mount
/srv/nfs4/data
, but of course can't, because/storage/data
doesn't exist yet:If I remove the bind mount from
/etc/fstab
, everything works fine (except my NFSv4 exports, of course).