From owner-freebsd-questions  Sun Feb 18 09:56:09 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA24464
          for questions-outgoing; Sun, 18 Feb 1996 09:56:09 -0800 (PST)
Received: from ejon.tiac.net (ejon.tiac.net [206.119.133.72])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA24437
          for <questions@freebsd.org>; Sun, 18 Feb 1996 09:55:59 -0800 (PST)
Received: (from ejon@localhost) by ejon.tiac.net (8.6.12/8.6.9) id MAA00247; Sun, 18 Feb 1996 12:55:22 -0500
From: Eric Jones <ejon@tiac.net>
Message-Id: <199602181755.MAA00247@ejon.tiac.net>
Subject: NQNFS problems
To: questions@freebsd.org
Date: Sun, 18 Feb 1996 12:55:22 -0500 (EST)
Cc: ejon@zipnet.net
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: owner-questions@freebsd.org
Precedence: bulk

Greetings,
	I'm having some odd behavoir from the NFS subsystem on 2.1-stable
(the kernel is from code sup'ed from the stable tree on about Feb 13th,
the rest of the distribution is from the stable tree on Dec 6).
	If I make changes inside an exported filesystem on the server
machine, the changes aren't always visible to the clients.  I haven't
waited any large amount of time to see if the changes are eventually
propagated.  If I umount/mount the filesystem, then things look normal
again.
	I'm using the leasing feature of the 4.4 NFS, so I can see how
the problem arises, but isn't the server supposed to revoke the lease
on files that change?

Thanks in advance for any advice you can offer.
Eric

P.S. Please CC me at ejon@tiac.net and ejon@zipnet.net