NFS problem
James F Davis
jim at thedavisnetwork.com
Mon Jan 26 05:06:10 UTC 2004
Not replying to help, but I'm experiencing the same problem with my nfs
shares. I think it might have something to with timing and iptables
locking up the related/established links before the server/client is
done talking. I'm running the nfsd on a slow ~200Mhz machine w/ USB
drives so there's a lot of latency that might be causing this problem.
I've knocked out the iptables holes for the server-ports to establish
the link but the problem occurs when the server/client start talking on
the pseudo-random high number ports...
Any ideas here?
Thanks,
Jim
-----Original Message-----
From: fedora-list-admin at redhat.com [mailto:fedora-list-admin at redhat.com]
On Behalf Of Robert Spangler
Sent: Sunday, January 25, 2004 23:58
To: fedora-list at redhat.com
Subject: NFS problem
Hello,
My systems
RedHat 9.0 Fedora (Laptop)
Host Client
2 shares
In Fedora's fstab I have defined the shares of the host. They are
defined
with the ip address. When I boot the Fedora machine it takes a long
time for
the nfs mounts to mount. After everything is up and running if I try to
ls
the shares it takes a long time too, and some times I see the following:
nfs: server x.x.x.x not responding, still trying
nfs: server x.x.x.x OK
nfs: server x.x.x.x not responding, still trying
nfs: server x.x.x.x OK
and then the directory is listed.
No both machine I have the following services up and running:
nfs
netfs
nfslock
portmap
network
I have asked on #fedora and was told that it is most likely a DNS issue
but
this i don't believe because the host lookup order is to first look in
hosts
file which all machines are defined.
Does anyone know of any other place or places I need to look?
Thnx
--
Regards
Robert
Smile..... It increases your face value.
--
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
More information about the fedora-list
mailing list