From owner-freebsd-questions Sat Nov 3 19: 1:13 2001 Delivered-To: freebsd-questions@freebsd.org Received: from pioneernet.net (mail.pioneernet.net [207.115.64.224]) by hub.freebsd.org (Postfix) with ESMTP id 2FCD137B405 for ; Sat, 3 Nov 2001 19:01:11 -0800 (PST) Received: from chip.wiegand.org [66.114.152.128] by pioneernet.net (SMTPD32-6.06) id AF844A030102; Sat, 03 Nov 2001 19:01:24 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Chip To: Dan Nelson Subject: Re: NFS mount won't unmount Date: Sat, 3 Nov 2001 20:07:52 -0700 X-Mailer: KMail [version 1.2] Cc: freebsd-questions@FreeBSD.ORG References: <0111022206152Y.96094@chip.wiegand.org> <20011104021157.GB92910@dan.emsphone.com> In-Reply-To: <20011104021157.GB92910@dan.emsphone.com> MIME-Version: 1.0 Message-Id: <0111031907522Z.96094@chip.wiegand.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday 03 November 2001 18:11, Dan Nelson wrote: > In the last episode (Nov 02), Chip said: > > I removed a computer from my network, which had nfs shares, and now on > > another machine I cannot umount that directory. I tried killall -HUP > > mountd but that didn't work. I cannot remove the directory name or > > unmount it, I just get device busy messages. Another sympton of this is > > when I am using KWrite, GVim, or any gui editor, and use file/open and > > navigate to the usr2 partition, it will hang and not show the two > > directories (the two differant nfs mounts from two other machines. One > > directory is the unmountable and the other is mounted and accessible from > > the term window, as regular user or root). I did search the archives > > which is where I found the killall -HUP mountd command. > > There must be a way to do this without a reboot? > > umount -f /mountpoint That doesn't work. Just results in a failed: device busy message. That 'device' no longer exists, it was shutdown, removed from the network, it's gone, it's no-more. So it is not possible for it to be busy. I realize I made a mistake by not unmounting this mountpoint prior to taking it down, now I would like to resolve this without a reboot. -- Chip W. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message