Date: Thu, 3 Oct 2002 09:29:48 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: Don Lewis <dl-freebsd@catspoiler.org>, current@FreeBSD.ORG Subject: Re: NFS hang on rmdir(2) with 5.0-current client, server Message-ID: <Pine.NEB.3.96L.1021003092851.55617G-100000@fledge.watson.org> In-Reply-To: <200210030943.aa86349@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Oct 2002, Ian Dowse wrote: > In message <Pine.NEB.3.96L.1021003020248.53997J-100000@fledge.watson.org>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1021003092851.55617G-100000>