NFS issues

I have a small home LAN. I am running FC15 on the server. As I still
have not made a full peace with FC15 I'm still running FC13 on the
client. Several years and FC versions ago, someone on the list told me
about this procedure for setting up NFS, which has been working fine...
until now.

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

On the server (192.168.1.14):

My /etc/exports file looks like this:
/home/magnusg/Music
192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)

Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.

I have services nfs and nfslock running on levels 3,4,5.

In /etc/sysconfig/nfs I've set these ports:
RQUOTAD_PORT=4000
LOCKD_TCPPORT=4001
LOCKD_UDPPORT=4001
MOUNTD_PORT=4002
STATD_PORT=4003

In the firewall I have these ports open:
NFSV4 2049 (tcp)
4000-4003 (tcp and udp)
111 (tcp and udp)

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

on the client (192.168.1.13):

I added this to /etc/fstab:
192.168.1.14:/home/magnusg/Music /home/magnusg/Music nfs
rw,auto,hard,intr,bg 0 0

Services netfs, nfslock and rpcbind are running on levels 3,4,5.

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

When I boot the client and get to the "Mounting NFS filesystems" section
I don't get error messages -- but I do see this:
mount.nfs: backgrounding 192.168.1.14:/home/magnusg/Music
: mount options
"hard,intr,bg,vers=4,addr=192.168.1.14,clientaddr=192.168.1.13"

Then I don't get a "Music" icon on my desktop, and when I open the
folder there's nothing in it.

Any advice on how to proceed would be appreciated.
Jerry





--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Relevant Pages

  • Errors writing large files via NFS
    ... files larger than a certain size to a NFS server. ... client systems, although the definition of "too large" varies. ... network paths involved, I'm pretty sure we're not seeing a network problem. ...
    (Tru64-UNIX-Managers)
  • Re: Still getting NFS client locking up
    ... > the same NFS lockups. ... > Reading from the server works perfectly all the time. ... > NFS CLIENT: ... in particular, look at traces for any client blocked in NFS, ...
    (freebsd-current)
  • Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram
    ... it gets the first ENOSPC error back from the server at around 1.5GB ... the data that gets ENOSPC errors is ... I'm no great expert but isn't this a design flaw in NFS? ... corruption because the NFS client thinks it has written the data ...
    (Linux-Kernel)
  • Re: [OT] Real time systems, was: Re: What is the draw of VMS?
    ... your nfs clients are going to hang. ... You can tell NFS to do soft mounts, if you find this acceptable, but the cost is data corruption. ... probing the server and running the highest level available. ... My client programs gets stuck until the server is back. ...
    (comp.os.vms)
  • Re: Problems mounting nfs from freebsd to Mac.
    ... Problems mounting nfs from freebsd to Mac. ... I've got an nfs server that's refusing to mount one client - via one ... That elimintes NFS on the client, and -most- of the NFS config on the ...
    (freebsd-questions)