> -----Original Message----- > From: Chuck Lever [mailto:chuck.lever@xxxxxxxxxx] > Sent: Wednesday, June 09, 2010 11:18 AM > To: Murata, Dennis > Cc: linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: FW: Unable to mount nfs directories RHEL 4.8 > > On 06/ 8/10 08:05 PM, Murata, Dennis wrote: > > Didn't see the original message, sorry if this is a duplicate > > > > -----Original Message----- > > From: Murata, Dennis > > Sent: Tuesday, June 08, 2010 3:26 PM > > To: linux-nfs-owner@xxxxxxxxxxxxxxx > > Subject: Unable to mount nfs directories RHEL 4.8 > > > > We are using a modified RHEL 4.8 build accessing Netapp filers for > > data directories. The build has nfs-utils-1.0.6-93.EL4, > > nfs-utils-lib-1.0.6-10.el4, kernel-largesmp-2.6.9-89.EL all x86_64. > > After a period of use, on a very questionable network using > tcp as the > > nfs transport, workstation will start getting error messages in > > /var/log/messages|dmesg and are not able to mount/access the data > > directories. A reboot is necessary to allow the mounts. The time > > period varies and seems to depend on the usage, but in general will > > start within a week of moderate use. The error messages are: > > > > lockd: cannot monitor 192.168.10.133 > > lockd: failed to monitor 192.168.10.133 > > nsm_mon_unmon: rpc failed, status=-96 > > lockd: cannot monitor 192.168.10.133 > > lockd: failed to monitor 192.168.10.133 > > nsm_mon_unmon: rpc failed, status=-96 > > lockd: cannot monitor 192.168.10.133 > > lockd: failed to monitor 192.168.10.133 > > > > These errors are repeated as access to the filer (ip > address has been > > changed) is tried. A ps on the workstation shows rpc.statd still > > running, service nfslock status reports rpc.statd running. > > Is portmap running, and is the statd service registered? Is > lockd registered for both UDP and TCP? Portmap is running. Not sure how to check if lockd is registered but the output from rpcinfo -p [root@host1 ~]# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100007 2 udp 880 ypbind 100007 1 udp 880 ypbind 100007 2 tcp 883 ypbind 100007 1 tcp 883 ypbind 100011 1 udp 948 rquotad 100011 2 udp 948 rquotad 100011 1 tcp 963 rquotad 100011 2 tcp 963 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100021 1 udp 34574 nlockmgr 100021 3 udp 34574 nlockmgr 100021 4 udp 34574 nlockmgr 100021 1 tcp 32786 nlockmgr 100021 3 tcp 32786 nlockmgr 100021 4 tcp 32786 nlockmgr 100005 1 udp 962 mountd 100005 1 tcp 974 mountd 100005 2 udp 962 mountd 100005 2 tcp 974 mountd 100005 3 udp 962 mountd 100005 3 tcp 974 mountd 100024 1 udp 744 status 100024 1 tcp 750 status [root@host1 ~]# > > > If the nfs-utils rpm from RHEL 4.6 is loaded, > nfs-utils-1.0.6-84.EL4, > > the problem does not occur. We have been testing a few > workstations > > for ~two weeks without problem. Any ideas? > > > > TIA > > Wayne > > -- > > To unsubscribe from this list: send the line "unsubscribe > linux-nfs" > > in the body of a message to majordomo@xxxxxxxxxxxxxxx More > majordomo > > info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
