From owner-freebsd-current Wed Feb 10 10:59:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03885 for freebsd-current-outgoing; Wed, 10 Feb 1999 10:59:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03879 for ; Wed, 10 Feb 1999 10:58:59 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id NAA10601 for current@freebsd.org; Wed, 10 Feb 1999 13:54:53 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199902101854.NAA10601@misha.cisco.com> Subject: Re: umount -f In-Reply-To: <19990210104842.A21617@relay.nuxi.com> from "David O'Brien" at "Feb 10, 1999 10:48:42 am" To: current@FreeBSD.ORG Date: Wed, 10 Feb 1999 13:54:53 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Will it ever work as it appears it should? Currently I have (on 2.2.8) > > > > mi@xxx:/tmp (1032) umount -f phosphorus:/phosphorus > > umount: /phosphorus: Device busy > > >From an email from Peter Wemm: > > In this situation, you need to do this: > umount -f -t nfs phosphorus:/phosphorus > > This causes umount to stat("phosphorus:/phosphorus") (which fails) rather > than "/mnt". Nope: mi@xxx:/tmp (1044) umount -f -t nfs phosphorus:/phosphorus umount: /phosphorus: Device busy It is not, that umount hangs, it is that it cares about the device being busy despite `-f' flag. Or so it seems... send-pr? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message