All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Dexuan Cui <decui@microsoft.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	'linux-ext4' <linux-ext4@vger.kernel.org>
Subject: Re: Can one file system be R/W mounted multiple times in Linux?
Date: Fri, 9 Jan 2015 06:55:46 -0800	[thread overview]
Message-ID: <20150109145546.GA26251@infradead.org> (raw)
In-Reply-To: <20150109120159.GA20300@stefanha-thinkpad.redhat.com>

On Fri, Jan 09, 2015 at 12:01:59PM +0000, Stefan Hajnoczi wrote:
> Can you explain under what conditions mounting the same file system
> twice will work?
> 
> I guess the kernel is looking up the block device and then sharing the
> superblock if the file system is already mounted on this block device?

Exactly.

> 
> If I use two loop devices for the same underlying storage it does not
> work:

Because that's very much the same situation as two different systems
trying to mount it.

  reply	other threads:[~2015-01-09 14:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  3:44 Can one file system be R/W mounted multiple times in Linux? Dexuan Cui
2015-01-09  3:51 ` Al Viro
2015-01-09  4:58   ` Dexuan Cui
2015-01-09  6:04     ` Eric Sandeen
2015-01-09  6:48       ` Dexuan Cui
2015-01-09 13:25         ` Bob Peterson
2015-01-09 12:01   ` Stefan Hajnoczi
2015-01-09 14:55     ` Christoph Hellwig [this message]
2015-01-09 15:52     ` Lukáš Czerner
2015-01-09 19:31       ` Pranay Srivastava
2015-01-09 20:37         ` Al Viro
2015-01-10  3:52           ` Dexuan Cui
2015-01-12 13:00       ` Karel Zak
2015-01-12 14:20         ` Lukáš Czerner
2015-01-12 16:47           ` Karel Zak

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=20150109145546.GA26251@infradead.org \
    --to=hch@infradead.org \
    --cc=decui@microsoft.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=stefanha@redhat.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.