Problem mounting NFS drive: "mount.nfs: mount system call failed"

Mr tim esquire · #1 5th October 2009, 11:15 PM

These are the settings on my server, which has a static ip:

Code:

[tim@computim ~]$ cat /etc/exports
/media/cavern                  192.168.1.*(rw,sync)

Code:

[tim@computim ~]$ cat /etc/hosts.deny
portmap:ALL
mountd:ALL
rquotad:ALL
statd:ALL
lockd:ALL

Code:

[tim@computim ~]$ cat /etc/hosts.allow    

portmap: 192.168.1.2/100
lockd: 192.168.1.2/100
rquotad: 192.168.1.2/100
mountd: 192.168.1.2/100
statd: 192.168.1.2/100

When i try to mount the disk from my client machine i get the error:

Code:

[tim@localhost ~]$ sudo mount -t nfs 192.168.1.10:/media/cavern /media/cavern
mount.nfs mount system call failed

Thinking the problem might be due to iptables i tried the foowing command as recomended by a book i found on google

Code:

sudo iptables -A INPUT -i wlan0 -f -j ACCEPT

didn't help so tried disabling the firewall - still getting the error

Both machines are running FC11 - should i be using nfs4?

thanks
t

robertmaessen · #2 6th October 2009, 06:56 PM

If you do "service nfs status"
it is telling you that:
rpc.mountd (pid ) is running...
nfsd (pid ) is running...
rpc.rquotad (pid ) is running...

Mr tim esquire · #3 6th October 2009, 07:47 PM

services running OK,
If i turn off both firewalls and comment out everything in hosts.allow and hosts.deny I can mount NFS OK. It will stay like this for now..

robertmaessen · #4 6th October 2009, 07:56 PM

Looking at the syntax of host allow "portmap: 192.168.1.2/100" after the / it suspects a netmask something like this.
IP Network with Subnet Mask: 192.168.1.0/255.255.255.0

robertmaessen · #5 6th October 2009, 08:04 PM

If you need to secure it better with hosts.allow use this
portmap: 192.168.1. allow
portmap : 192.168.1.1 deny

Mr tim esquire · #6 6th October 2009, 08:22 PM

It seems nfs4 is the way forward here. I scrapped the above, turned the firewalls back on and allowed nfs4 with the firewall manager. works a charm!

robertmaessen · #7 6th October 2009, 08:27 PM

Yep, NFS4 is the better way these days, since most directory's are just linked into the NFS4 repository you don't have nasty things like "you can not run this or that on a fileshare directory on the fileshare server itself"

Mr tim esquire · #8 6th October 2009, 11:43 PM

Currently using the below line in my /etc/fstab on the client machine to load the exports from the server. Unfortunately this only loads the first share on the exports list.

Code:

#nfs4
192.168.1.10:/ /media/computim/ nfs4 _netdev,auto 0 0

If your setting up a networked fileserver or shared disk just take a look at nfs4 howTos youll get there in the end (and i hope I will too)

peas!