From owner-freebsd-current Tue Nov 7 13: 4:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id B845237B479 for ; Tue, 7 Nov 2000 13:04:53 -0800 (PST) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 101F11C83; Tue, 7 Nov 2000 16:04:53 -0500 (EST) Date: Tue, 7 Nov 2000 16:04:53 -0500 From: Bill Fumerola To: Warner Losh Cc: current@freebsd.org Subject: Re: umount -f busted Message-ID: <20001107160452.R37870@jade.chc-chimes.com> References: <200011072013.NAA22410@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200011072013.NAA22410@harmony.village.org>; from imp@village.org on Tue, Nov 07, 2000 at 01:13:41PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Mount with 'intr,soft' for better luck with this. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message