[Bug 1515446] [NEW] NFS shares in FSTAB no longer mount at boot
Launchpad Bug Tracker
1515446 at bugs.launchpad.net
Thu Jan 21 00:22:25 UTC 2016
You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):
After a fresh install of 15.10, nfs shares no longer mount on boot.
I'm using the same line to mount as I did in 14.04 prior:
<server>:/share /mnt/share ntfs4 _netdev, auto 0 0
This line worked just fine in 14.04, and 14.10 on my laptop, to mount
the shares at boot.
Manual mounting after boot works fine. Systemctl shows a name
resolution failure (see below)
lsb_release -rd
Description: Ubuntu 15.10
Release: 15.10
lsb_release -rd
Description: Ubuntu 15.10
Release: 15.10
bjwest at razorback:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:
*** 1:1.2.8-9ubuntu10 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
systemctl status mnt-share.mount
● mnt-share.mount - /mnt/share
Loaded: loaded (/etc/fstab)
Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 15s ago
Where: /mnt/share
What: hog:/share
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev (code=exited, status=32)
Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server hog: Temporary failure in name resolution
Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, code=exited status=32
Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed state.
** Affects: hundredpapercuts
Importance: Medium
Status: Confirmed
** Affects: network-manager (Ubuntu)
Importance: Medium
Status: Confirmed
** Affects: systemd (Ubuntu)
Importance: Medium
Status: Confirmed
** Tags: patch wily
--
NFS shares in FSTAB no longer mount at boot
https://bugs.launchpad.net/bugs/1515446
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list