From: Calvin Walton <calvin.walton@kepstin.ca>
To: Wolfgang Mader <Wolfgang_Mader@brain-frog.de>,
linux-btrfs@vger.kernel.org
Subject: Re: Concurrent write access
Date: Fri, 17 Jul 2015 14:12:31 -0400 [thread overview]
Message-ID: <1437156751.22061.4.camel@kepstin.ca> (raw)
In-Reply-To: <1598536.6uUjd689JJ@discus>
On Fri, 2015-07-10 at 00:13 +0200, Wolfgang Mader wrote:
> On Thursday 09 July 2015 22:06:09 Hugo Mills wrote:
> > On Thu, Jul 09, 2015 at 11:34:40PM +0200, Wolfgang Mader wrote:
> > > Hi,
> > >
> > > I have a btrfs raid10 which is connected to a server hosting
> > > multiple virtual machine. Does btrfs support connecting the same
> > > subvolumes of the same raid to multiple virtual machines for
> > > concurrent read and write? The situation would be the same as,
> > > say,
> > > mounting user homes from the same nfs share on different
> > > machines.
> >
> > It'll depend on the protocol you use to make the subvolumes
> > visible
> > within the VMs.
> >
>
> Thanks for the overview. It it qmeu/kvm in fact, to this is an
> option. Right
> now, however, I connect the discs as virtual discs and not the file
> system,
> but only to one virtual machine.
btrfs is *not* a cluster filesystem, so one key thing it does not
support is having the same block device being mounted by multiple
computers at the same time (doesn't matter if they're hardware or
virtual machines).
Note that all the subvolumes on a btrfs filesystem share some core data
structures, so mounting different subvolumes is not a way to work
around this limitation.
If you mount the filesystem on the host machine then use a network
protocol (like nfs,samba,9p mentioned earlier), everything will be ok.
If you actually want to mount a filesystem from the same block device
on multiple VMs, you'll have to look into using a specially-designed
cluster filesystem like OCFS or GFS.
--
Calvin Walton <calvin.walton@kepstin.ca>
prev parent reply other threads:[~2015-07-17 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 21:34 Concurrent write access Wolfgang Mader
2015-07-09 22:06 ` Hugo Mills
2015-07-09 22:13 ` Wolfgang Mader
2015-07-17 18:12 ` Calvin Walton [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=1437156751.22061.4.camel@kepstin.ca \
--to=calvin.walton@kepstin.ca \
--cc=Wolfgang_Mader@brain-frog.de \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).