NetBSD Problem Report #1247

From gnats  Thu Jul 20 10:55:08 1995
Received: from Collatz.McRCIM.McGill.EDU (root@Collatz.McRCIM.McGill.EDU [132.206.78.1]) by sun-lamp.pc.cs.cmu.edu (8.6.11/8.6.10) with ESMTP id KAA03738 for <gnats-bugs@gnats.netbsd.org>; Thu, 20 Jul 1995 10:55:03 -0400
Message-Id: <199507201454.KAA19351@Collatz.McRCIM.McGill.EDU>
Date: Thu, 20 Jul 1995 10:54:41 -0400
From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
Reply-To: mouse@Collatz.McRCIM.McGill.EDU
To: gnats-bugs@gnats.netbsd.org
Subject: [dM] umount -f and unmount(2)'s MNT_FORCE flag don't work right
X-Send-Pr-Version: 3.2

>Number:         1247
>Category:       kern
>Synopsis:       [dM] umount -f and unmount(2)'s MNT_FORCE flag don't work right
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    fvdl
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 20 11:05:02 +0000 1995
>Closed-Date:    Fri Dec 13 08:49:09 +0000 2002
>Last-Modified:  Fri Dec 13 08:49:09 +0000 2002
>Originator:     der Mouse
>Release:        19950720
>Organization:
	Dis-
>Environment:
	SPARC IPC, but UTSLing makes me think it doesn't matter
>Description:
	umount(8)'s -f flag, and unmount(2)'s MNT_FORCE flag, can under
	some circumstances fail to unmount a filesystem.
>How-To-Repeat:
	# mount -r someserver:/some/file/system /mnt
	# ( cd /mnt ; sleep 999999 ) &
	[1] 1234
	# umount -f /mnt
	umount: /mnt: Device busy
	# kill %1

	[1]    Terminated           ( cd /mnt; sleep 999999 )
	# umount -f /mnt
	#
>Fix:
	Not known.  I do notice that kern/vfs_syscalls.c:dounmount()
	checks vfs_busy() before it checks for MNT_FORCE, which is
	probably the cause of the problem.  I don't know whether this
	is fixable; if not, maybe this should be treated as a doc-bug,
	and the documentation for umount(8) -f and unmount(2) MNT_FORCE
	updated to note that even when they're used the filesystem may
	not be unmounted.

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: kern-bug-people->fvdl 
Responsible-Changed-By: lukem 
Responsible-Changed-When: Mon Jun 25 14:02:26 PDT 2001 
Responsible-Changed-Why:  
Frank might be able to resolve this one as well 
State-Changed-From-To: open->feedback 
State-Changed-By: jdolecek 
State-Changed-When: Thu Dec 12 09:48:46 PST 2002 
State-Changed-Why:  
The umount -f succeeds for me when I try it with 1.6K. Okay to close 
the PR? 

From: der Mouse <mouse@Rodents.Montreal.QC.CA>
To: jdolecek@netbsd.org
Cc: fvdl@netbsd.org, gnats-bugs@netbsd.org
Subject: Re: kern/1247
Date: Fri, 13 Dec 2002 01:23:39 +0100 (CET)

 > The umount -f succeeds for me when I try it with 1.6K. Okay to close
 > the PR?

 Sure, if everything earlier has been EOLed. :-)

 But seriously, yes, if it's now fixed, it seems appropriate to just
 close the PR.

 /~\ The ASCII				der Mouse
 \ / Ribbon Campaign
  X  Against HTML	       mouse@rodents.montreal.qc.ca
 / \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
State-Changed-From-To: feedback->closed 
State-Changed-By: jdolecek 
State-Changed-When: Fri Dec 13 00:48:36 PST 2002 
State-Changed-Why:  
Problem isn't present anymore with 1.6K apparently. 
Thanks for report. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.