Comment 3 for bug 1582854

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.