From owner-freebsd-current  Sun Jul 23 23:05:12 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id XAA03364
          for current-outgoing; Sun, 23 Jul 1995 23:05:12 -0700
Received: from throck.cdrom.com (throck.cdrom.com [192.216.222.24])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id XAA03354
          for <current@freefall.cdrom.com>; Sun, 23 Jul 1995 23:05:07 -0700
Received: (from jkh@localhost) by throck.cdrom.com (8.6.11/8.6.9) id XAA00457 for current@freefall; Sun, 23 Jul 1995 23:05:51 -0700
Date: Sun, 23 Jul 1995 23:05:51 -0700
From: "Jordan K. Hubbard" <jkh@freebsd.org>
Message-Id: <199507240605.XAA00457@throck.cdrom.com>
To: current@freefall.cdrom.com
Subject: Interesting NFS problem with -current
Sender: current-owner@freebsd.org
Precedence: bulk

Scenario:  Several hosts with cross-mount privs managed by AMD.  Host foo
exports its cdrom drive to host bar, which can see it in /host/foo/cdrom.
So far, so good.  Now say that foo unmounts the CD in the drive and mounts
a new one.  Host bar now sees:

	<some command>: /host/foo/cdrom: Stale NFS file handle

In response to any access to the newly mounted CD.  At the
same time as the access, host foo prints:

fhtovp: file start miss 60 vs 20

On its system console.

I figure this is something to do with NFS v3, but perhaps the data
is of use to someone working in that area.

				Jordan