Date: Tue, 7 Nov 2000 13:41:01 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: Warner Losh <imp@village.org> Cc: Bill Fumerola <billf@chimesnet.com>, current@FreeBSD.ORG Subject: Re: umount -f busted Message-ID: <20001107134101.C5112@fw.wintelcom.net> In-Reply-To: <200011072114.OAA22975@harmony.village.org>; from imp@village.org on Tue, Nov 07, 2000 at 02:14:04PM -0700 References: <20001107160452.R37870@jade.chc-chimes.com> <200011072013.NAA22410@harmony.village.org> <20001107160452.R37870@jade.chc-chimes.com> <200011072114.OAA22975@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Warner Losh <imp@village.org> [001107 13:14] wrote: > 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! Yes, this used to work quite well for some time, I have no idea who broke it. Maybe you can sprinkle some printfs in the code and narrow it down a bit? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001107134101.C5112>