From owner-freebsd-current Thu Oct 9 11:00:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16275 for current-outgoing; Thu, 9 Oct 1997 11:00:51 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16260 for ; Thu, 9 Oct 1997 11:00:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id TAA02909; Thu, 9 Oct 1997 19:59:03 +0200 (CEST) To: Karl Denninger cc: Robin Cutshaw , freebsd-current@FreeBSD.ORG Subject: Re: NFS cache problem in 3.0 SNAP In-reply-to: Your message of "Thu, 09 Oct 1997 12:02:08 CDT." <19971009120208.12168@Mars.Mcs.Net> Date: Thu, 09 Oct 1997 19:59:03 +0200 Message-ID: <2907.876419943@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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 ? 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 phk@FreeBSD.ORG "Real hackers run -current on their laptop."