NFS issues -- fixed but not solved

Gerhard Magnus magnus at agora.rdrop.com
Tue Nov 8 21:41:52 UTC 2011


Restating the problem:

On the server, running FC15 (192.168.1.14):
(1) My /etc/exports file looks like this:
/home/magnusg/Music  192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
(2) Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.
(3) I have services nfs and nfslock running on levels 3,4,5.
(4) In /etc/sysconfig/nfs I've set these ports:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003
(5) In the firewall I have these ports open:
NFSV4 2049 (tcp)
4000-4003 (tcp and udp)
111 (tcp and udp)

on the client, running FC13 (192.168.1.13):
(1) I added this to /etc/fstab:
192.168.1.14:/home/magnusg/Music /home/magnusg/Music nfs
rw,auto,hard,intr,bg 0 0
(no change by adding option "nfsvers=3" which has made this work in the
past.)
(2) Services netfs, nfslock and rpcbind are running on levels 3,4,5.

...but /home/magnusg/Music won't mount on the client, either during the
boot or when I use the mount command later: mount.nfs: access denied by
server while mounting PuteF:/home/magnusg/Music

--------------------

I fixed the problem by installing FC14 on the server. It's amazing the
linux problems that simply disappear by avoiding all use of the disaster
that is FC15!

I can understand the rationale for making users go through a big song
and dance in order to play mp3 files, but stuff like scp and nfs should
be as simple to set up on a LAN as they are easy to use.





More information about the users mailing list