Date: Sun, 26 Jan 2003 16:35:11 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.ORG> To: Tim Kientzle <kientzle@acm.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: umount of procfs fails Message-ID: <Pine.NEB.3.96L.1030126163022.24134K-100000@fledge.watson.org> In-Reply-To: <3E344532.50007@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Jan 2003, Tim Kientzle wrote: > Experimenting with 'mount' and stumbled across the following oddity: > > mount -t procfs proc /mnt > umount -t /mnt You're missing the "proc" after -t here, right? > results in procfs still mounted on /mnt but no longer mounted on /proc. > It appears that a umount of procfs is unmounting the most recently > mounted instance rather than the instance mounted at the specified > location. > > I haven't checked to see if other filesystem types have this problem. I experimented a bit, and found the following: If I unmount /mnt using simply "umount /mnt" on -CURRENT or -STABLE, /mnt is unmounted. If I specify "-t procfs", the same thing happens. If I mis-specify the mount type as "-t proc", then it silently fails, and neither is unmounted. Which isn't to say that it didn't happen for you, but you should probably provide a bit more information. First, could you identify the version of FreeBSD you're running? Second, can you include script output of the shell session in which you mount /proc, /mnt, run mount to confirm they are both mounted, then umount one, run mount to show the wrong one unmounted? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030126163022.24134K-100000>