Comment 0 for bug 365772

Revision history for this message
Ryan Ritterson (rrpublic) wrote :

Binary package hint: nfs-common

For some time I was affected by bug #213444, preventing me from mounting an NFS share since Ubuntu 8.04 (Gutsy). That bug appears to have been fixed (for a short time i was able to mount successfully), but now I get an additional series of errors in Jaunty when trying to mount an NFS share:

call: sudo mount -t nfs -o nolock -vvvv fileserver:/remoteMount localmount
which returns:
mount.nfs: mount(2): Input/output error

and

mount.nfs: mount system call failed.

We have a number of other linux systems around, running different distributions, mostly CentOS, which have no problem mounting the server.

Of interest may be a link dumped into the system logs:

muscat kernel: [ 979.924016] rpcbind: server fileserver not responding, timed out

However, I think that's probably a red herring, as mount typically responds with a different error message on time out, and other computers are able to reach the NFS server without difficulty.

iptables has no rules set up, and portmapper is running. I have also tried -o nolock (as you can see), but it appears I am affected by a different problem than bug #306016.

Package is version 1:1.1.4-1ubuntu1