From owner-freebsd-bugs  Thu Oct  2 23:40:06 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA23560
          for bugs-outgoing; Thu, 2 Oct 1997 23:40:06 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA23539;
          Thu, 2 Oct 1997 23:40:02 -0700 (PDT)
Date: Thu, 2 Oct 1997 23:40:02 -0700 (PDT)
Message-Id: <199710030640.XAA23539@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: David Muir Sharnoff <muir@idiom.com>
Subject: Re: kern/4666: umount -f doesn't seem to work
Reply-To: David Muir Sharnoff <muir@idiom.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4666; it has been noted by GNATS.

From: David Muir Sharnoff <muir@idiom.com>
To: j@uriah.heep.sax.de (J Wunsch)
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/4666: umount -f doesn't seem to work
Date: Thu, 2 Oct 1997 23:34:37 -0700 (PDT)

 * As muir@idiom.com wrote:
 * 
 * >     tmp:/	 /net/tmp  nfs	ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0
 * >     tmp:/usr /net/tmp/usr  nfs	ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0
 * > 
 * > >Description:
 * > 
 * > 	 # umount -f -h tmp
 * > 	 nfs server tmp:/: not responding
 * 
 * This is what one would expect how umount -f is working, but not what
 * is described for umount -f: forcibly unmounting is currently only
 * defined as ``don't care about resources that are locally still in use,
 * but revoke them''.
 * 
 * Anyway, i think this is already in Doug Rabson's queue of ``nice to
 * have'' things.  If i'm not totally mistaken, there might already be
 * another open PR for it.  Did you check before filing?
 
 No.  It seemed like a bug to me.
 
 -Dave