mount -t nfs not working in ubuntu 16.04

Bug #1582854 reported by Manfred Grabherr on 2016-05-17
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
High
Unassigned

Bug Description

After upgrading from 15.10 to 16.04, the command

sudo mount -t nfs Biest:/<path_to_shared_dir> /home/manfred/BigDisk/

times out without any further error reporting:

mount.nfs: Connection timed out

It worked on the same machine before the upgrade, and it still works from both a 14.04 and a 15.10 machine. The file server is running 14.04.

Additional info: I just updated today (05/17/2016). Let me know what else you need. Other people seem to have the same or similar problems, but no official bug report, fix, or workaround to be found. Only viable option I have now is to downgrade to 15.10.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mount 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 17 20:57:58 2016
InstallationDate: Installed on 2015-06-27 (325 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: util-linux
UpgradeStatus: Upgraded to xenial on 2016-04-30 (16 days ago)

Update: there seems to be a much deeper networking problem, perhaps introduced with kernel update 4.4.0-22. Mounting Windows shares/samba also does not work any more. Neither does network printing. The only things still working are ssh and sftp.

After a lot of digging, I found a solution/workaround. The problem is the nfs version, in short:

sudo mount -t nfs o nfsvers=2 server:/<serverdir> <localdir>

does the trick. Anyway, here is what happens without specifying the nfsvers option:

sudo mount -t nfs -v server:/<serverdir> <localdir>

mount.nfs: timeout set for Sat May 21 11:59:43 2016
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.133,clientaddr=192.168.1.25'
mount.nfs: mount(2): Stale file handle

Version 3 also does not work:

sudo mount -t nfs -v o nfsvers=3 server:/<serverdir> <localdir>

mount.nfs: timeout set for Sat May 21 12:00:12 2016
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.133'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.133 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.133 prog 100005 vers 3 prot UDP port 55187
mount.nfs: mount(2): Stale file handle

Finally, this does work:

sudo mount -t nfs -v o nfsvers=2 server:/<serverdir> <localdir>

mount.nfs: timeout set for Sat May 21 12:00:33 2016
mount.nfs: trying text-based options 'nfsvers=2,addr=192.168.1.133'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.1.133 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: trying 192.168.1.133 prog 100005 vers 1 prot UDP port 34856

Again, the NFS server runs Ubuntu Desktop 14.04, nfs export is done without any specific options wrt the nfs version.

So maybe this is not a bug per se and it is just that the default for the version has changed, but IMHO, a meaningful error message would be *a lot* better than just timing out without any additional information.

Phillip Susi (psusi) on 2016-07-05
affects: util-linux (Ubuntu) → nfs-utils (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in nfs-utils (Ubuntu):
status: New → Confirmed
Changed in nfs-utils (Ubuntu):
importance: Undecided → High
Len Davis (ldavis-e) wrote :

I am also seeing this when trying to nfs mount Solaris 10 file systems.

Mike Hawke (mhawke) wrote :

I am also seeing this bug on Ubuntu 16.04.3 LTS 4.4.0-93-generic 64bit, issue occurs randomly, when it happens i am no longer able to mount the device with nfs v3, however using v2 works.
Please look into this bug, its been more than a year since it was originally reported.

Thanks

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers