From owner-freebsd-current  Mon Oct 13 03:11:56 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id DAA08615
          for current-outgoing; Mon, 13 Oct 1997 03:11:56 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA08603
          for <freebsd-current@freebsd.org>; Mon, 13 Oct 1997 03:11:49 -0700 (PDT)
          (envelope-from dfr@nlsystems.com)
Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2])
	by nlsystems.com (8.8.5/8.8.5) with SMTP id LAA28501;
	Mon, 13 Oct 1997 11:09:28 +0100 (BST)
Date: Mon, 13 Oct 1997 11:09:28 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
Reply-To: Doug Rabson <dfr@nlsystems.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
cc: Karl Denninger <karl@Mcs.Net>, Robin Cutshaw <robin@intercore.com>,
        freebsd-current@freebsd.org
Subject: Re: NFS cache problem in 3.0 SNAP 
In-Reply-To: <2907.876419943@critter.freebsd.dk>
Message-ID: <Pine.BSF.3.95q.971013110610.958A-100000@herring.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 9 Oct 1997, 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 ?
> 
> 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 ?

The nfs client calls nfs_invaldir when it detects a directory chance I
think.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 951 1891
					Fax:   +44 181 381 1039