From owner-freebsd-current Wed Oct 2 22:59: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FFF537B401 for ; Wed, 2 Oct 2002 22:59:05 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BEB843E65 for ; Wed, 2 Oct 2002 22:59:04 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g935wTOo056284; Thu, 3 Oct 2002 01:58:29 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 3 Oct 2002 01:58:28 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Don Lewis Cc: current@FreeBSD.ORG Subject: Re: NFS hang on rmdir(2) with 5.0-current client, server In-Reply-To: <200210030554.g935sovU017799@gw.catspoiler.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2 Oct 2002, Don Lewis wrote: > On 2 Oct, Robert Watson wrote: > > > > Running into an odd (and apparently recent) problem involving rmdir(2) and > > NFS. I have a diskless box started using pxeboot: NFS /, MFS /var, MFS > > /tmp, recent 5.0-CURRENT. Attempt to rmdir /usr/local (on NFS) results in > > NFS hanging. It appears to send out the RPC, but no response comes back > > from the (also recent) FreeBSD 5.0 NFS server. Here's the quicky on the > > client: > > > It looks like the client is basically hung waiting for an RPC response. > > I'd be glad to provide more debugging information if someone can point me > > in the right direction. > > I haven't seen this seen this problem with a 5.0-CURRENT client and a > 4.7-PRERELEASE server, so as near as I can tell the client side isn't > totally hosed. I pointed my client at a Solaris server and it seems not to be a problem in that configuration, leading me to suspect the server. I'm going to twiddle kernels a bit and see if it's a local problem of some sort or not. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message