From owner-freebsd-stable  Wed Dec 24 02:54:56 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA29763
          for stable-outgoing; Wed, 24 Dec 1997 02:54:56 -0800 (PST)
          (envelope-from owner-freebsd-stable)
Received: from silvia.HIP.Berkeley.EDU (ala-ca34-23.ix.netcom.com [207.93.143.151])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA29733
          for <stable@FreeBSD.ORG>; Wed, 24 Dec 1997 02:54:51 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id CAA26943; Wed, 24 Dec 1997 02:54:40 -0800 (PST)
Date: Wed, 24 Dec 1997 02:54:40 -0800 (PST)
Message-Id: <199712241054.CAA26943@silvia.HIP.Berkeley.EDU>
To: jdp@polstra.com
CC: stable@FreeBSD.ORG
In-reply-to: <199712231712.JAA26683@austin.polstra.com> (message from John Polstra on Tue, 23 Dec 1997 09:12:12 -0800)
Subject: Re: Bogus interaction between NFS and mount
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * It is hard to see why mounting a local CD-ROM on the NFS server should
 * cause problems for a completely separate exported file system, but
 * that is what is happening.  The only connection between the CD-ROM and
 * NFS, as far as I can tell, is that /cdrom happens to be exported.

I noticed that when you change anything about an exported filesystem
(for instance "mount -u -o async") on an NFS server, mountd goes and
re-checks all the filesystems.  The filesystems are un-exported while
it's doing this, and can cause the symptoms you described even if the
client is using a different filesystem.

 * Suggestions, anyone?

No idea. :)

Satoshi