** Description changed:
+ Fix is described in comment #23
+
NOW:
*ubuntu since 7.11 - meaning at the moment 8.04 and 8.10 releases can't
reliably mount NFS exports without getting "mount.nfs: internal error" if done
from the command line.
If the mount request is in /etc/fstab it stops KDE loading and the
system becomes unuseable (unless you know to open another TTY session).
The only workaround (for most people) is to set the mount to "noauto" in
/etc/fstab and try to mount it until it succeeds at the command prompt
when the system is booted.
WAS:
Using Ubuntu Studio based on Hardy Heron beta, 64-bit w/AMD Athlon 64 x2. The
other computer involved is a 32-bit Sempron running Gutsy Gibbon. I followed
instructions on http://czarism.com/easy-peasy-ubuntu-linux-nfs-file-sharing to
make a directory on the Gutsy system availalble on the Hardy beta system, and
got the following message when I attempted the mount:
mount.nfs: internal error
I double checked the commands and the IP addresses/ranges involved, and
they appear to be correct.
At the Gutsy end: nfs-common and nfs-kernel-server are
1:1.1.1~git-20070709-3ubuntu1, portmap is 6.0-1ubuntu1.
At the Hardy end: 1:1.1.2-2ubuntu2 and 6.0-4 for the same packages,
respectively.
** Changed in: nfs-utils (Ubuntu Hardy)
Status: New => Triaged
** Changed in: nfs-utils (Ubuntu Hardy)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/213444
Title:
8.04 & 8.10 nfs clients report "internal error" when attempting to
mount NFS exports
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
