From muir@news.idiom.com  Wed Oct  1 00:03:01 1997
Received: from news.idiom.com (news.idiom.com [140.174.82.35])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA23778
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 1 Oct 1997 00:03:00 -0700 (PDT)
Received: (from muir@localhost)
	by news.idiom.com (8.8.7/8.8.5) id AAA08206;
	Wed, 1 Oct 1997 00:02:59 -0700 (PDT)
Message-Id: <199710010702.AAA08206@news.idiom.com>
Date: Wed, 1 Oct 1997 00:02:59 -0700 (PDT)
From: muir@idiom.com
Reply-To: muir@idiom.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: umount -f doesn't seem to work
X-Send-Pr-Version: 3.2

>Number:         4666
>Category:       kern
>Synopsis:       umount -f doesn't seem to work
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    dfr
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct  1 00:10:01 PDT 1997
>Closed-Date:    Mon Feb 25 03:56:51 PST 2002
>Last-Modified:  Mon Feb 25 03:57:48 PST 2002
>Originator:     David Muir Sharnoff
>Release:        FreeBSD 2.2-STABLE i386
>Organization:
Idiom
>Environment:

	2.2-STABLE system, mounting disks from a 2.2-STABLE system
	with the following options...

    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
	 # umount -f /net/tmp
	 nfs server tmp:/: not responding
	 # umount -f /net/tmp/usr
	 nfs server tmp:/: not responding
	 # df
	 nfs server tmp:/: not responding

	 I should mention that the machine formerly known as 'tmp' is
	 currently in the mail.

>How-To-Repeat:

	Mount a filesystem as above.  Turn of the NFS server and mail
	it somewhere.  Try to unmount the disks without cheating.

>Fix:
	
	

>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: muir@idiom.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/4666: umount -f doesn't seem to work
Date: Wed, 1 Oct 1997 17:10:51 +0200

 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?
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)

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
Responsible-Changed-From-To: freebsd-bugs->dfr 
Responsible-Changed-By: joerg 
Responsible-Changed-When: Sun Oct 19 20:24:36 MEST 1997 
Responsible-Changed-Why:  
Doug is our Mr. NFS. 
State-Changed-From-To: open->closed 
State-Changed-By: iedowse 
State-Changed-When: Mon Feb 25 03:56:51 PST 2002 
State-Changed-Why:  

Fixed in both -CURRENT and -STABLE. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=4666 
>Unformatted:
