Date: Wed, 10 Feb 1999 10:48:42 -0800 From: "David O'Brien" <obrien@NUXI.com> To: mi@aldan.algebra.com Cc: current@FreeBSD.ORG Subject: Re: umount -f Message-ID: <19990210104842.A21617@relay.nuxi.com> In-Reply-To: <199902101814.NAA10513@misha.cisco.com>; from Mikhail Teterin on Wed, Feb 10, 1999 at 01:14:54PM -0500 References: <199902101814.NAA10513@misha.cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Will it ever work as it appears it should? Currently I have (on 2.2.8)
>
> mi@xxx:/tmp (1032) umount -f phosphorus:/phosphorus
> umount: /phosphorus: Device busy
>From an email from Peter Wemm:
In this situation, you need to do this:
umount -f -t nfs phosphorus:/phosphorus
This causes umount to stat("phosphorus:/phosphorus") (which fails) rather
than "/mnt".
I really don't understand all the reasons behind this, but there seems to
be a result of a lot of hackery so that:
ln -s /dev/wd0c /dev/cdrom
mount /dev/cdrom /mnt
umount /dev/cdrom /mnt
.. works. I don't recall the problems that it has to work around, but I
gather that at mount time the symlink is followed and "/dev/wd0c" is
installed in the mount table - so "/dev/cdrom" would not be matched by
umount(2).
-----
bde commented that the current behavior is needed so that "/dev/cdrom"
shows up in ``mount'' w/o args instead of "/dev/wd0c".
--
-- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
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?19990210104842.A21617>