From hsu@clinet.fi  Mon Nov 27 18:48:08 1995
Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA23973
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 27 Nov 1995 18:48:07 -0800
Received: (root@localhost) by hauki.clinet.fi (8.6.12/8.6.4) id EAA02241; Tue, 28 Nov 1995 04:47:53 +0200
Message-Id: <199511280247.EAA02241@hauki.clinet.fi>
Date: Tue, 28 Nov 1995 04:47:53 +0200
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: stale nfs mounts cannot be umounted
X-Send-Pr-Version: 3.2

>Number:         841
>Category:       bin
>Synopsis:       stale nfs mounts cannot be umounted
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 27 18:50:03 PST 1995
>Closed-Date:    Sat Dec 18 15:40:03 PST 1999
>Last-Modified:  Sat Dec 18 15:41:01 PST 1999
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2-CURRENT i386
>Organization:
Clinet, Espoo, Finland
>Environment:

	a stale nfs mount, like this one:

df: /m/hauki/customer: Stale NFS file handle

>Description:

Trying to umount it fails:

hsu#katiska.clinet.fi Tue 163: umount /m/hauki/customer
umount: hauki.clinet.fi:/m/hauki/customer: No such file or directory

hsu#katiska.clinet.fi Tue 165: umount -f /m/hauki/customer
umount: hauki.clinet.fi:/m/hauki/customer: No such file or directory

hsu#katiska.clinet.fi Tue 166: mount /m/hauki/customer
mount: /m/hauki/customer: Stale NFS file handle

So the only way to get rid of it is to reboot the machine.  On FreeBSD
1.1.5.1 -f is enough, on SunOS it can be umounted if there are no stale
handles on the mounted filesystem (killing holders of them fixes that).

>How-To-Repeat:

	Get a disk crash on your nfs server and try to get things up
	again.  A big hammer will probably do, if you don't happen to own
	any barracudas.

>Fix:
	
	Force option should do something?

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:14:21 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->closed 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:46:28 PDT 1996 
State-Changed-Why:  

Problem Still Exists 

--- 

From: Heikki Suonsivu <hsu@clinet.fi> 
Subject: FreeBSD PR: bin/841 


I haven't got stale mounts around right now but as this also can be 
produced with "permission denied" mounts, it seems still to be valid bug 
report. 

hsu#zetor.clinet.fi Tue 12: umount /m/katiska/news1 
umount: katiska.clinet.fi:/m/katiska/news1: No such file or directory 
hsu#zetor.clinet.fi Tue 13: umount -f /m/katiska/news1 
umount: katiska.clinet.fi:/m/katiska/news1: No such file or directory 
hsu#zetor.clinet.fi Tue 14: 
df: /m/katiska/news1: Permission denied 
df: /m/katiska/news2: Permission denied 

State-Changed-From-To: closed->open 
State-Changed-By: scrappy 
State-Changed-When: Tue Oct 22 02:31:09 PDT 1996 
State-Changed-Why:  


I 'oops' this one...should have been changed back to open, not closed... 

State-Changed-From-To: open->suspended 
State-Changed-By: phk 
State-Changed-When: Mon Apr 13 01:34:41 PDT 1998 
State-Changed-Why:  
-> suspended 
State-Changed-From-To: suspended->closed 
State-Changed-By: green 
State-Changed-When: Sat Dec 18 15:40:03 PST 1999 
State-Changed-Why:  
This has been fixed in -CURRENT and 3.3/3.4. 
>Unformatted:
 
 
