From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org
Subject: OK to mount multiple FS in one dir?
Date: Mon, 05 Feb 2001 03:08:50 +0000 [thread overview]
Message-ID: <3A7E1942.5090903@goingware.com> (raw)
I was groping around my FAT/NTFS directories from Linux, mounting and
unmounting them into
/mnt, and was suprised at some point that I got the message "/dev/sda5
already mounted or
/mnt busy". (I'm using a SCSI disk, use hda* for IDE).
Upon further examination, I found that I'd accidentally mounted
/dev/sda1 (VFAT) on /mnt
while /dev/sda5 (NTFS) was still mounted there. The NTFS files remained
invisible until
I'd unmounted /dev/sda1 and then I could see them again.
This is with the 2.4.1 kernel on a Pentium III machine with an Adaptec
29160 SCSI
controller.
I found I could mount three partitions on /mnt, and they'd all show up
as mounted at
/mnt in the "mount" command, but if I unmounted one of them (only tried
with the currently
visible one), then it appeared that there were no filesystems mounted
there, but I could
continue umounting until the other two were gone.
I'm suprised this works. Note that the kernel rejected an attempt to
mount a filesystem
that was already mounted, but not to mount a filesystem at a point that
was already in use.
It looks like there is a stack of mounts on the mount point.
Looking at Documentation/Changes, I see that I need util-linux 2.10o. I
had 2.10l. But I
had the 2.10r util-linux sources on my machine and installed mount and
umount from it, and
I find that it gets it right mostly when I mount and unmount multiple
things, with the
exception that if /dev/sda5 was mounted before /dev/sda1, then if I give
the command
"umount /dev/sda5", sda1 is the one that gets unmounted rather than
sda5, so it takes the
most recently mounted filesystem rather than the one you specify.
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com
Tilting at Windmills for a Better Tomorrow.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-05 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 3:08 Michael D. Crawford [this message]
2001-02-06 0:06 ` OK to mount multiple FS in one dir? Peter Samuelson
2001-02-06 19:47 ` Thorsten Glaser Geuer
2001-02-06 20:46 ` Wakko Warner
2001-02-07 6:25 ` Peter Samuelson
2001-02-07 7:00 ` John R Lenton
2001-02-25 6:10 ` Alexander Viro
2001-02-07 22:49 ` David L. Nicol
2001-02-25 6:12 ` Alexander Viro
2001-02-25 6:08 ` Alexander Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A7E1942.5090903@goingware.com \
--to=crawford@goingware.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox