From owner-freebsd-current Tue Nov 7 13:14:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id ACE4A37B4C5 for ; Tue, 7 Nov 2000 13:14:07 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eA7LE5g10047; Tue, 7 Nov 2000 14:14:05 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA22975; Tue, 7 Nov 2000 14:14:04 -0700 (MST) Message-Id: <200011072114.OAA22975@harmony.village.org> To: Bill Fumerola Subject: Re: umount -f busted Cc: current@freebsd.org In-reply-to: Your message of "Tue, 07 Nov 2000 16:04:53 EST." <20001107160452.R37870@jade.chc-chimes.com> References: <20001107160452.R37870@jade.chc-chimes.com> <200011072013.NAA22410@harmony.village.org> Date: Tue, 07 Nov 2000 14:14:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001107160452.R37870@jade.chc-chimes.com> Bill Fumerola writes: : On Tue, Nov 07, 2000 at 01:13:41PM -0700, Warner Losh wrote: : : > I just tried to umount -f /home, where /home was an NFS mounted file : > system on a network that was no longer attached to my laptop. In the : > past this has just worked, even if processes were hung in disk wait : > state. When I tried it last night on an Oct 29th kernel, I got EBUSY : > and the file system remained mounted. : > : > This can't be right. Is there any way to really force it short of a : > reboot? : : That's just the way it seems to be. It didn't used to be this way. : Mount with 'intr,soft' for better luck with this. Things weren't stuck in disk wait, but they still returned EBUSY. Force means force, damnit! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message