[CentOS] NFS issues
johan.swensson at apegroup.com
Wed Aug 13 13:48:54 UTC 2008
> Johan Swensson wrote:
>> No firewall on either end and server responds to ping.
>> program vers proto port
>> 100000 2 tcp 111 portmapper
>> 100000 2 udp 111 portmapper
>> 100024 1 udp 889 status
>> 100024 1 tcp 892 status
> Doesn't look like nfslock is running on the client?
> What does /etc/init.d/nfslock status say?
[root at web03 ~]# service nfslock status
rpc.statd (pid 2737) is running...
>> As Craig said he started notice this about the the time he upgraded to
>> 5.2, the same goes for me, started getting this problem about the time
>> I've upgraded the clients and server.
> Maybe related to this bug:
> Try restarting nfslock on both client and server when it occurs?
> Or try setting up a cron to restart nfslock hourly on all systems
> to see if that can workaround the issue until a fix comes out?
Actually I tried restarting both nfslock(on clients and server) and
nfs(on server) but it didn't help.
Is my solution with mounting it nolock bad?
I was also thinking about mounting the nfs shares as soft, is this a
good idea? Could it help me? And also, what's the difference between
soft and intr?
Read the manual and I thought they were pretty similiar.
> CentOS mailing list
> CentOS at centos.org
More information about the CentOS