From: Chuck Lever Subject: Re: FW: Unable to mount nfs directories RHEL 4.8 Date: Wed, 09 Jun 2010 12:18:24 -0400 Message-ID: <4C0FBED0.9030809@oracle.com> References: <620E93B2E5CC3B46BD811165E3335B8708C2A04E@0461-its-exmb02.us.saic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Cc: linux-nfs@vger.kernel.org To: "Murata, Dennis" Return-path: Received: from rcsinet10.oracle.com ([148.87.113.121]:65516 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756899Ab0FIQTG (ORCPT ); Wed, 9 Jun 2010 12:19:06 -0400 In-Reply-To: <620E93B2E5CC3B46BD811165E3335B8708C2A04E-9/h0XwadXgnyjpQT3Si/rsM9+qvyE0V4QQ4Iyu8u01E@public.gmane.org> Sender: linux-nfs-owner@vger.kernel.org List-ID: 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@vger.kernel.org > 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? > 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html