From owner-freebsd-current Thu Oct 3 6:30:24 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 1FA9E37B401 for ; Thu, 3 Oct 2002 06:30:23 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B737643E6E for ; Thu, 3 Oct 2002 06:30:21 -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 g93DTmOo059563; Thu, 3 Oct 2002 09:29:49 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 3 Oct 2002 09:29:48 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ian Dowse Cc: Don Lewis , current@FreeBSD.ORG Subject: Re: NFS hang on rmdir(2) with 5.0-current client, server In-Reply-To: <200210030943.aa86349@salmon.maths.tcd.ie> 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 Thu, 3 Oct 2002, Ian Dowse wrote: > In message , Robe > rt Watson writes: > >> > 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. > > > >Interesting observation: rm on files, and rmdir on empty directories > >doesn't trigger it, but attempt to rmdir on a non-empty directory does. > > This an NFSv2 mount, and I think the problem is specific to NFSv2. > Something like the following patch should fix it. I probably missed > this in revision 1.112 when fixing some similar issues in other > server op functions. See the commit message for that revision for > further details. You are right--for whatever reason, we mount NFSv2 as the default in a diskless boot, and the patch you provide me with seems to clear up the problem. Thanks, 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