shares not mounted on boot

Bug #1537779 reported by Timo Aaltonen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

If fstab uses hostname(s) instead of IP address(es), the NFS shares wont get mounted if and when the server name fails to resolve. The network seems to get up a few seconds after the system tries to mount the shares.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nfs-common 1:1.2.8-9ubuntu11
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 25 16:44:28 2016
InstallationDate: Installed on 2016-01-22 (3 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: nfs-utils
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.statd-mounting.override: manual
upstart.statd.override: manual

Revision history for this message
Timo Aaltonen (tjaalton) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nfs-utils (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.