From: Stefan Hajnoczi <stefanha@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: 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 12:01:59 +0000 [thread overview]
Message-ID: <20150109120159.GA20300@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20150109035123.GG22149@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Fri, Jan 09, 2015 at 03:51:23AM +0000, Al Viro wrote:
> On Fri, Jan 09, 2015 at 03:44:16AM +0000, Dexuan Cui wrote:
> > The 'mount' utility allows me to mount 1 file systems multiple times at different
> > mount points, like "mount /dev/sdb1 /a; mount /dev/sdb1 /b".
> >
> > I tried to write from /a and /b at the same time and it seems everything is OK
> > and no data corruption happens.
> > I tried only ext4 only.
> >
> > Can somebody please tell me if this usage is safe?
>
> Yes.
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?
If I use two loop devices for the same underlying storage it does not
work:
# mount -o loop /var/tmp/ext4.img /tmp/a
# mount -o loop /var/tmp/ext4.img /tmp/b
# touch /tmp/a/a
# ls /tmp/b
lost+found
# umount /tmp/a
# umount /tmp/b
# mount -o loop /var/tmp/ext4.img /tmp/a
[1078357.297245] EXT4-fs error (device loop0): ext4_lookup:1441: inode #2: comm ls: deleted inode referenced: 12
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-09 12:02 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 [this message]
2015-01-09 14:55 ` Christoph Hellwig
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=20150109120159.GA20300@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=decui@microsoft.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).