From owner-freebsd-current  Tue Jul 25 19:26:26 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id TAA26658
          for current-outgoing; Tue, 25 Jul 1995 19:26:26 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id TAA26647
          ; Tue, 25 Jul 1995 19:26:22 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id TAA26319; Tue, 25 Jul 1995 19:24:05 -0700
To: Doug Rabson <dfr@render.com>
cc: "Jordan K. Hubbard" <jkh@freebsd.org>, current@freefall.cdrom.com
Subject: Re: Interesting NFS problem with -current 
In-reply-to: Your message of "Mon, 24 Jul 1995 12:00:54 BST."
             <Pine.BSF.3.91.950724115416.12542C-100000@minnow.render.com> 
Date: Tue, 25 Jul 1995 19:24:05 -0700
Message-ID: <26316.806725445@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: current-owner@freebsd.org
Precedence: bulk

> When a server changes a disk in its CD drive, all the clients should remount
> the filesystem to get a new root filehandle.  With AMD, the only thing you
> can do is to reduce the timeout on the client or forcible unmount it using
> something like:
> 	
> 	amq -u /host/foo/cdrom

Sorry for the original misdiagnosis.  I still think that this is something
that the server should deal with in a little less hostile a fashion
though.  Having to reaquire a whole new mount handle just because a CD
swapped out of a drive seems a little..  extreme..

					Jordan