I am running Ubuntu 16.04. Since upgrading from 14.04 to 16.04, I have found that the 'auto' fstab mount option no longer mounts NFS volumes on access. I found that I need to use the x-systemd.automount fstab option to automount my NFS volumes on access.
However, if the NFS volume is inaccessible, e.g. I am not on a network, the desktop freezes permanently (no timeout) when I go to the desktop menu. I think that is because two of the NFS mounts are listed under "Places". Also, 'df' hangs in such cases. I am using these mount options:
async,soft,noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,intr,_netdev
When the permanent hang happens, the only solution is to log into a character screen and modify /etc/fstab to comment out the NFS entry and reboot.
Is this expected? Is there a new way to accomplish this?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Wed Mar 21 10:00:11 2018
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HotplugNewDevices:
HotplugNewMounts:
InstallationDate: Installed on 2017-09-27 (174 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: linux-hwe
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
Monitoring the udisks daemon. Press Ctrl+C to exit.
10:00:39.847: The udisks-daemon is running (name-owner :1.52).
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bruce 1549 F.... pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=f5ace785-df36-4261-8716-0f9472574ae1
InstallationDate: Installed on 2017-09-27 (225 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 2353ABU
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=c4bbf5e7-4310-43b8-bfc7-115433a90ab4 ro
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
RelatedPackageVersions:
linux-restricted-modules-4.13.0-39-generic N/A
linux-backports-modules-4.13.0-39-generic N/A
linux-firmware 1.157.17
Tags: xenial
Uname: Linux 4.13.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/04/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETA7WW (2.67 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2353ABU
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG7ETA7WW(2.67):bd05/04/2017:svnLENOVO:pn2353ABU:pvrThinkPadT430s:rvnLENOVO:rn2353ABU:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2353ABU
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1757442
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.