From: Bob Peterson <rpeterso@redhat.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: Eric Sandeen <esandeen@redhat.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
linux-ext4 <linux-ext4@vger.kernel.org>,
stefanha@redhat.com
Subject: Re: Can one file system be R/W mounted multiple times in Linux?
Date: Fri, 9 Jan 2015 08:25:15 -0500 (EST) [thread overview]
Message-ID: <404451928.6537116.1420809915626.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <F792CF86EFE20D4AB8064279AFBA51C61EA7288F@SIXPRD3002MB028.064d.mgd.msft.net>
> > >>> Can somebody please tell me if this usage is safe?
> > >>
> > >> Yes.
> > But to be clear, just in case - this is completely different from, say,
> > mounting the
> > same ext4 fs on two different nodes on a SAN, which is quite certainly not
> > safe...
> >
> > -Eric
>
> Thank Eric for pointing this out!
> Can you please explain this? I didn't use SAN...
>
> Thanks,
> -- Dexuan
Hi Dexuan,
I think Eric means mounting the same physical device from two different
machines (whether they be VMs or nodes in a cluster, etc.) where shared
storage is involved (like SAN or iSCSI). If one system has no knowledge
of what the other is changing, the file system will likely be corrupted.
It sounds like you're probably not doing that.
However, shared file systems like gfs2 and ocfs2 are designed to allow
simultaneous R/W access from multiple nodes, and the file system metadata
is kept in sync and coherent across the cluster.
I don't know if gfs2 allows multiple mounts from the same machine to
different mount points, due to how its inter-node locking and journal
recovery are coordinated. (I haven't tried it in recent years).
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2015-01-09 13:25 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 [this message]
2015-01-09 12:01 ` Stefan Hajnoczi
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=404451928.6537116.1420809915626.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=decui@microsoft.com \
--cc=esandeen@redhat.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 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).