I solved the problem by updating to nfs-common-1.2.2-1ubuntu1 and nfs-
kernel-server-1.2.2-1ubuntu1 (both taken from maverick), and the related
am-utils problem by updating to am-utils-6.2+rc20110530-1ubuntu1, taken
from oneiric (luckily all the prerequsites for these packages are
fulfilled by
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nfs-utils (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/680680
Title:
I'm running a Debian Server (6.0.3) and two Ubuntu 10.04 LTS clients with
am-utils to mount the server shares.
On the 10.04 LTS, the output of 'mount' and '/proc/mounts' differ about the
nfs-version and the used protocol type:
~$ mount | grep nfs | grep home
seth:(pid1718,port1022) on /home
Following the above hint from Peter Bell, I've now added the proto and
vers options to the amd.home-map (beside that, I set the rsize and wsize
to 16k). Demanded are the following options:
~$ ypcat -k amd.home | grep 'default '
/defaults
I have just discovered that 'mount.nfs' defaults to applying the option
'vers=4'. This was causing me problems with nfs3 mounts via autofs. I
presume that this behaviour is a change between 10.04 and 10.10, since I
never encountered this difficulty in Lucid.
If this was an intentional change, I
--
mount picks the wrong version of NFS filesystem
https://bugs.launchpad.net/bugs/680680
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
mount.nfs is intended to be a helper for /sbin/mount, you shouldn't
really be invoking it directly. Is this problem reproducible if you
call 'mount -tnfs' instead of 'mount.nfs'?
--
mount picks the wrong version of NFS filesystem
https://bugs.launchpad.net/bugs/680680
You received this bug
'mount -t nfs' was where I was originally seeing the problem. I switched to
mount.nfs afterwards so there would be one less possibility of a failure
point.
I tried the basic 'mount -t nfs' on a clean 10.04 install and it worked. So
it appears to be something that was introduced between then and
