From owner-freebsd-current Thu Oct 9 11:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA17809 for current-outgoing; Thu, 9 Oct 1997 11:22:00 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA17798 for ; Thu, 9 Oct 1997 11:21:53 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id NAA06172; Thu, 9 Oct 1997 13:21:47 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id NAA00660; Thu, 9 Oct 1997 13:21:46 -0500 (CDT) Message-ID: <19971009132146.18909@Mars.Mcs.Net> Date: Thu, 9 Oct 1997 13:21:46 -0500 From: Karl Denninger To: Poul-Henning Kamp Cc: Karl Denninger , Robin Cutshaw , freebsd-current@FreeBSD.ORG Subject: Re: NFS cache problem in 3.0 SNAP References: <19971009120208.12168@Mars.Mcs.Net> <2907.876419943@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <2907.876419943@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Oct 09, 1997 at 07:59:03PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Oct 09, 1997 at 07:59:03PM +0200, Poul-Henning Kamp wrote: > In message <19971009120208.12168@Mars.Mcs.Net>, Karl Denninger writes: > >> > >> I just upgraded to 3.0-971003-SNAP and have an NFS client problem. If > >> I change a file on the NFS server (FreeBSD 2.2.1), the change does not > >> show up on the 3.0 client > > > >This is a problem that I reported some time ago, and it remains open. > > > >Its actually quite a bit more serious than you might think; look for my > >previous message in the archives for the exact behavior(s) that are > >exhibited under different conditions. > > I backed my VOP_LOOKUP change out recently, I pressume that improved > the situation a bit or hur ? Uh, when? I just looked through the commitlogs for sys and didn't see it.... > I'm wondering if we need a call from the nfs code to the namecache > when the nfs code decides that a directory has been changed. Anybody > know where we can detect that situation ? > > -- > Poul-Henning Kamp FreeBSD coreteam member Not offhand, no. The problem we see here which is very repeatable is this: Boxes (1 and 2, server is on system 3 which is not involved) 1: mv file1 file2 2: cat file1 (still works) 1: cp file3 file1 2: cat file1 (still shows OLD contents of file 1) 1: rm file1 2: cat file1 (STILL shows old contents - you've now lost the ability to get at the handle which was there first!) This is bad. Here's another: 1: rm file1 2: cat file1 (returns "Stale NFS handle" - not file not found!) 1: cp file3 file1 2: cat file1 (now shows proper content; it "fixed itself") -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal