Workaround: add the 'bootwait' option to the /home fstab entry.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1384502
Title:
fstab entry for nfs /home fails to mount on
I am experiencing the same problem in UbuntuStudio 15.10.
I have the following line in /etc/fstab:
dwf:/volume1/dwf_data /media/nfs_dwf nfs auto 0 0
the error at boot is the follwing:
mount.nfs: Failed to resolve server dwf: Temporary failure in name
resolution
I do not get errors when
Please disregard the last comment, that was unfortunately for a
different bug that affects 14.10 only.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1384502
Title:
fstab
Ok, I've investigated this, and it turn out:
statd-mounting.conf intercepts nfs mounts and waits for the statd daemon to be
run
statd.conf starts on (virtual-filesystems and started portmap ON_BOOT=y)
rpcbind.conf is what emits the started portmap event:
# For compatibility with older upstart jo
Same here with an 14.10 AMD64 installation on a KVM machine.
The workaround with "mount -a" in rc.local doesn't help much for daemons
that need the mounted NFS share at startup. They're failing when the
mount isn't present at boot time.
I've stopped further deployment of Utopic until this bug has
Confirmed. The issue here is that as an NFS mount not mounted under
/usr or /var, mountall implicitly treats this as 'nobootwait'. It's
debatable whether this should be done, but the other issue is that
filesystems being marked 'nobootwait' doesn't just prevent them from
blocking the boot, it als
`mountall --verbose` log w/ip addr in fstab
** Attachment added: "mountall.log.ipaddr"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242077/+files/mountall.log.ipaddr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
** Attachment added: ".var.log.upstart.mountall.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242076/+files/.var.log.upstart.mountall.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: ".etc.network.interfaces"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+attachment/4242075/+files/.etc.network.interfaces
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in
i also attempted a boot w/the nfs server's ip address instead of
hostname (although technically i guess "nfs-home" is an alias). no
change, /home was still not mounted automatically on boot by mountall.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
10 matches
Mail list logo
