From owner-freebsd-current Sat Sep 27 16:07:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA18892 for current-outgoing; Sat, 27 Sep 1997 16:07:00 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA18879 for ; Sat, 27 Sep 1997 16:06:55 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id QAA14147; Sat, 27 Sep 1997 16:03:03 -0700 (MST) From: Terry Lambert Message-Id: <199709272303.QAA14147@usr03.primenet.com> Subject: Re: WARNING! Builds from the last few days have BROKEN NFS To: karl@mcs.net (Karl Denninger) Date: Sat, 27 Sep 1997 23:03:02 +0000 (GMT) Cc: phk@critter.freebsd.dk, karl@mcs.net, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <19970927150755.39452@Mars.Mcs.Net> from "Karl Denninger" at Sep 27, 97 03:07:55 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If you look on the other system, a "ls" doesn't show the errant file. > But a "cat" does -- the data is still there. Needless to say this is > pretty troublesome, and leads to lots of head-scratching. This will opccur on two occasions: 1) The file has been deleted, but the vnode was not removed from the cache, so you get a cache hit on open, and the file is still displayable after it has (nominally) been deleted. This points to an error in the name cache code. 2) The open call is OK, but the readdir is broken; the open will succeed, because it does it's own (linear) traversal, but the readdir fails because it does a cookie-based per block traversal. This points to an error in the cookie code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.