public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: /proc/mounts: two different loop devices mounted on same mountpoint?!
Date: Thu, 28 Feb 2002 15:28:52 +0100	[thread overview]
Message-ID: <20020228152852.B23019@devcon.net> (raw)
In-Reply-To: <20020228095948.GG774@elf.ucw.cz> <Pine.LNX.4.33.0202281200230.15246-100000@unicef.org.yu> <20020228134455.GA28490@atrey.karlin.mff.cuni.cz>
In-Reply-To: <20020228134455.GA28490@atrey.karlin.mff.cuni.cz>; from pavel@suse.cz on Thu, Feb 28, 2002 at 02:44:55PM +0100

On Thu, Feb 28, 2002 at 02:44:55PM +0100, Pavel Machek wrote:
> 
> > I think that is normal behaviour in 2.4.X
> > that one can mount more than once
> > on same mount point.
> But two different devices? What's the semantics, then?

All accesses go to the filesystem mounted last. The one mounted first
is inaccessible until you unmount the filesystem covering it. Well,
not really inaccessible, if any process happened to have a working
directory or an open file on the first filesystem at the time you
mounted the second, it can still access it.

There is nothing special involved, after all, it's the same as if you
mount a single filesystem to /mnt, the only difference is that the
second mount this time doesn't cover a single dirtree on the root
partition, but instead it covers a complete other filesystem.

Andreas
-- 
       Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
     ---------------------------------------------------------
         +49 521 1365800 - af@devcon.net - www.devcon.net

      reply	other threads:[~2002-02-28 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28  9:59 /proc/mounts: two different loop devices mounted on same mountpoint?! Pavel Machek
2002-02-28 11:02 ` Davidovac Zoran
2002-02-28 13:44   ` Pavel Machek
2002-02-28 14:28     ` Andreas Ferber [this message]

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=20020228152852.B23019@devcon.net \
    --to=aferber@techfak.uni-bielefeld.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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