NFS share mounting problem

[amdlin]

Ubuntu 10.10RC

- mount method 1: (manual try):
x@x-laptop:~$ sudo mount -t nfs -v 192.168.1.1:/tmp/mnt/disc1_6 /mnt/disc1_6
mount.nfs: timeout set for Fri Oct 1 00:42:51 2010
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.1,clientaddr=192.168.1.249'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.1,clientaddr=192.168.1.249'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.1,clientaddr=192.168.1.249'
mount.nfs: mount(2): Connection refused
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.1,clientaddr=192.168.1.249'
mount.nfs: mount(2): Connection refused

***The NFS server log doesn't show any client's connection attempts

- mount method 2: (automatic by fstab)
/etc/fstab contains following
192.168.1.1:/tmp/mnt/disc1_6 /mnt/disc1_6 nfs rsize=32768,wsize=32768,intr,noatime
reboot

Note:
1) Both mounting methods are working fine with ubuntu 10.04 (i have second laptop with 10.04 installed, so it was easy for me to check)
2) The re-instalation of maveric nfs-common 1:1.2.2-1ubuntu1 package will not resolve the problem
3) The deinstalation of nfs-common 1:1.2.2-1ubuntu1 and installing nfs-common_1%3a1.2.0-4ubuntu4_i386 (package from ubuntu 10.04) on Maveric has resolved the problem

Conclusion:
It has to be something wrong with standart nfs-common package shipping with Maveric.
As a temprorary solution is using the nfs-common package from previous ubuntu (Lucid)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nfs-common 1:1.2.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Oct 1 00:45:57 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nfs-utils

[Aleksandr Tarasenko (jtaa)]

same problem

[Douglas Brick (dbrick-kom)]

I was having this same problem mounting one, older, machine, but not any of the others. I found that specifying proto=udp in the mount options seemed to fix it. Not sure why this was necessary with that older machine and not with the others.

[Markus Schulz (schulz-alpharesearch)]

Also the proto=udp fixed it for me!

[amdlin (amdlintuxos)]

proto=udp works for me as well

[Bryce Harrington (bryce)]

$ sudo mount -t nfs -v 192.168.1.1:/tmp/mnt/disc1_6 /mnt/disc1_6
mount.nfs: timeout set for Fri Oct 1 00:42:51 2010
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.1,clientaddr=192.168.1.249'

Was it intended for the client to specify vers=4? I.e. could this just be a mixup of nvs 3 vs 4 between the client and server? (Ala bug #680680 or #117957)

[Ramesh (ramesh-rr7)]

Been having the same issue but proto=udp did not work for me. My server is running a uclibc compiled unfs3. No issues with ubuntu version of unfs3. On a whim, I tried to install a natty nfs-common package (http://packages.ubuntu.com/natty/amd64/nfs-common/download) using dpkg. Got an error: "nfs-common depends on portmap (>= 6.0.0-2ubuntu3)", but interestingly, mounting nfs now works! Version of nfs-common installed is now 1:1.2.2-4ubuntu4.