[FIXED] NFS Networking Fails with incorrect mount option

[NoWorries]

I have now upgraded both my desktop (sybil) and laptop (basil) to 11.10. For several years now, NFS has worked successfully. I have been using the same procedures and now they no longer work and come back with error. The error message on basil is:

An error occurred while accessing '/home/aurora on sybil', the system responded: mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

My hosts file on basil has:

127.0.0.1	localhost
127.0.1.1	basil
192.168.10.4	sybil

# The following lines are desirable for IPv6 capable hosts
::1   ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

And my hosts.allow on basil has:

# /etc/hosts.allow: list of hosts that are allowed to access the system.
#          See the manual pages hosts_access(5) and hosts_options(5).
#
# Example:  ALL: LOCAL @some_netgroup
#       ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8) and rpc.mountd(8)
# for further information.
#
# Sybil
portmap: 192.168.10.4
lockd: 192.168.10.4
rquotad: 192.168.10.4
mountd: 192.168.10.4
statd: 192.168.10.4
sshd: 192.168.10.4
nfsd: 192.168.10.4

Naturally my hosts.deny has ALL: ALL

My exports file on basil has:

# /etc/exports: the access control list for filesystems which may be exported
#		to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes    hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4    gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/		192.168.10.0/255.255.255.0(rw,sync,no_subtree_check)
/home/aurora	192.168.10.0/255.255.255.0(rw,sync,no_subtree_check)

Last but not least my fstab on basil has:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc      /proc      proc  nodev,noexec,nosuid 0    0
# / was on /dev/sda1 during installation
UUID=4129747b-fcd9-40e7-b916-359003a93eff /        ext4  errors=remount-ro 0    1
# /home was on /dev/sda6 during installation
UUID=9907d3c8-c432-436d-ad5a-dd8058fb4713 /home      ext4  defaults    0    2
# swap was on /dev/sda5 during installation
UUID=f8873d15-e093-4c05-bd73-db0c56efd552 none      swap  sw       0    0
# NFS Mounts
sybil:/home/aurora   /home/aurora/aurora/sybil_home   nfs  rw,user,noauto,hard,intr  0  0

I have the complementary entries on sybil to access basil.

As far as i can tell this is an outstanding kernel bug. Has anyone been able to get around this NFS problem or even get NFS to work? It is such a pain to no longer have NFS available .

[sithlord48]

Re: NFS Networking Fails with incorrect mount option

have you installed all the required packages. im thinking you missed one like "portmap" i have NFS on all my machines no such issues.

[vinnywright]

Re: NFS Networking Fails with incorrect mount option

I allso am using NFS on my 11.10 box to access files on a 10.04 box .

all I had to do on the 11.10 box was was issue the mount command after making the mount point

sudo mount -t nfs 192.168.2.5:/home/vinny/ /mnt/desk1

the 10.04 box is runing the server part.

it looks from your error like rpc.statd is not running so like @sithlord48 sead check portmap is installed.

VINNY

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

have you installed all the required packages. im thinking you missed one like "portmap" i have NFS on all my machines no such issues.

I could not find portmap in my repositories. When I did an apt-get on the nfs packages including portmap I get the following:

:~$ sudo apt-get install nfs-kernel-server nfs-common portmap
Reading package lists... Done
Building dependency tree    
Reading state information... Done
Note, selecting 'rpcbind' instead of 'portmap'
nfs-common is already the newest version.
nfs-kernel-server is already the newest version.
rpcbind is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

So I think the use of rpcbind instead of portmap is the problem but since it is not available for me I am wondering if there is something wrong with my repositories.

[oshunluvr]

Re: NFS Networking Fails with incorrect mount option

Try sudo /etc/init.d/statd restart and then sudo mount -a and report.

There was a bug back in 10.04 that should have been fixed.

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

Try sudo /etc/init.d/statd restart and then sudo mount -a and report.

There was a bug back in 10.04 that should have been fixed.

Thanks for the advice. What I get is shown below:

:~$ sudo /etc/init.d/statd restart
[sudo] password:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service statd restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) and then start(8) utilities,
e.g. stop statd ; start statd. The restart(8) utility is also available.
statd stop/waiting
statd start/running, process 2310
:~$ sudo mount -a
:~$

The mount gives no output and the network files are not mounted.
Are you able to get portmap on your system?

[oshunluvr]

Re: NFS Networking Fails with incorrect mount option

Sorry, I didn't notice you have "noauto" on your NFS mounts.

Try mounting them manually.

[vinnywright]

Re: NFS Networking Fails with incorrect mount option

Are you able to get portmap on your system?

it dosent appear to be in the 11.10 repo .......what seams necessary are nfs-common and rpcbind

VINNY

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

Sorry, I didn't notice you have "noauto" on your NFS mounts.

Try mounting them manually.

I use "noauto" as I find it more convenient to mount when required. This is done simply by clicking on the file shown in the sidebar of Dolphin. I have found problems with a computer that is still running and when the PC associated with the mounted file is shutdown. The manual mount gives the same error as with Dolphin, namely:

mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

I have tried specifying the actual device IP address instead of the symbolic name as well as alternate directory to mount to. All give the same error.

I am still wondering why I cannot find "portmap" in my repositories, as I think its absence is the source on my troubles.

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

Are you able to get portmap on your system?

it dosent appear to be in the 11.10 repo .......what seams necessary are nfs-common and rpcbind

VINNY

Well my problems are certainly very obscure as I have both "nfs-common" and "rpcbind" installed .

[oshunluvr]

Re: NFS Networking Fails with incorrect mount option

My last comment referred to "mount -a" not working because your mounts were noauto. I access my NFS shares all the time, so they're always mounted.

mount.nfs: an incorrect mount option was specified

This will tell you if portmapper is running: rpcinfo -p

Sample output:

  program vers proto  port
  100000  2  tcp  111 portmapper
  100000  2  udp  111 portmapper
  100024  1  udp 36525 status
  100024  1  tcp 55377 status
  100021  1  udp 33779 nlockmgr
  100021  3  udp 33779 nlockmgr
  100021  4  udp 33779 nlockmgr
  100021  1  tcp 54519 nlockmgr
  100021  3  tcp 54519 nlockmgr
  100021  4  tcp 54519 nlockmgr

I am working with 11.04, so portmap is still in he repos. You could be having "beta" trouble.

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

Currently my Laptop network has utterly failed while testing changes to my exports file. I cannot make any wired or wireless connections. I have no idea what I did to cause this problem. I checked the system with my installation disc and all is well with the hardware for my wired and wireless connections. I am currently on my Desktop downloading the latest build to reinstall and start all over again.

I only had problems with nfs when I upgraded both systems to oneiric. On my Desktop with no laptop connected I get the following:

:~$ rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 50979 status
100024 1 tcp 42544 status
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 2 tcp 2049
100227 3 tcp 2049
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100227 2 udp 2049
100227 3 udp 2049
100021 1 udp 52746 nlockmgr
100021 3 udp 52746 nlockmgr
100021 4 udp 52746 nlockmgr
100021 1 tcp 37078 nlockmgr
100021 3 tcp 37078 nlockmgr
100021 4 tcp 37078 nlockmgr
100005 1 udp 39720 mountd
100005 1 tcp 59589 mountd
100005 2 udp 42907 mountd
100005 2 tcp 51011 mountd

What I currently think is the source of my problem is the export file. In it I had the wild card address line :

/home/aurora	 192.168.10.0/255.255.255.0(rw,sync,no_subtree_check)

When I get my system back up again, I will try a host name instead. Unfortunately we will be going out to dinner tonight (OZ time that is!) and I am not sure how I will go time-wise doing a reinstall without annoying my wife too much.

[oshunluvr]

Re: NFS Networking Fails with incorrect mount option

Other than the IP address and a couple of missing options, the export line above looks just like mine.

The network is a problem obviously. Are you using KNetworkManager?

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

Other than the IP address and a couple of missing options, the export line above looks just like mine.

The network is a problem obviously. Are you using KNetworkManager?

Yes, I am using KNetworkManager and I have now done a reinstall. Fortunately I finished it before we went out last night as my wife wanted to do some emails so I excused myself to get the Laptop working. I now have all networking in a perfect running state. This allowed me to quickly configure the email package that runs on my Laptop to be brought up on my Wife's desktop for her to do the email while I finished the installation of packages.

Unfortunately I have no idea why I could not get NFS networking previously. I am no expert, but I am wondering if a faulty ca-certificates package was implicated in causing my network to be totally creamed. Certainly, "portmap" is no longer required in 11.10 and I have used my original exports file to verify that it was not the culprit in my NFS problems.

I have now changed my exports file line from:

/home/aurora	192.168.10.0/255.255.255.0(rw,sync,no_subtree_check)

to:

/home/aurora	sybil(rw,sync,no_subtree_check)

Where "sybil" is my Wife's computer name that is defined in the hosts file with the IP address.

I have found that with the new version, I can used Dolphin to mount with a single click on the network symbol and unmount with a right mouse click . With the previous version the unmount fails with a busy message. This means that under these condition when I shut down, I have to use the power button.

So thanks for all the help and I am glad that I now have a tidier NFS network files that allows either machine to be up or down without ill effects.

[NoWorries]

Re: NFS Networking Fails with incorrect mount option

Other than the IP address and a couple of missing options, the export line above looks just like mine.

The network is a problem obviously. Are you using KNetworkManager?

Yes, I am using KNetworkManager and I have now done a reinstall. Fortunately I finished it before we went out last night as my wife wanted to do some emails so I excused myself to get the Laptop working. I now have all networking in a perfect running state. This allowed me to quickly configure the email package that runs on my Laptop to be brought up on my Wife's desktop for her to do the email while I finished the installation of packages.

Unfortunately I have no idea why I could not get NFS networking previously. I am no expert, but I am wondering if a faulty ca-certificates package was implicated in causing my network to be totally creamed. Certainly, "portmap" is no longer required in 11.10 and I have used my original exports file to verify that it was not the culprit in my NFS problems.

I have now changed my exports file line from:

/home/aurora	192.168.10.0/255.255.255.0(rw,sync,no_subtree_check)

to:

/home/aurora	sybil(rw,sync,no_subtree_check)

Where "sybil" is my Wife's computer name that is defined in the hosts file with the IP address.

I have found that with the new version, I can used Dolphin to mount with a single click on the network symbol and unmount with a right mouse click . With the previous version the unmount fails with a busy message. This means that under these condition when I shut down, I have to use the power button.

So thanks for all the help and I am glad that I now have tidier NFS network files that allow either machine to be up or down without ill effects.