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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1582854 Title: mount -t nfs not working in ubuntu 16.04 Status in util-linux package in Ubuntu: New 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1582854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
