From owner-freebsd-current Tue Nov 7 12:13:50 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 345F437B479 for ; Tue, 7 Nov 2000 12:13:48 -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 eA7KDgg09802 for ; Tue, 7 Nov 2000 13:13:46 -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 NAA22410 for ; Tue, 7 Nov 2000 13:13:41 -0700 (MST) Message-Id: <200011072013.NAA22410@harmony.village.org> To: current@freebsd.org Subject: umount -f busted Date: Tue, 07 Nov 2000 13:13:41 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message