linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Mader <Wolfgang_Mader@brain-frog.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Concurrent write access
Date: Fri, 10 Jul 2015 00:13:42 +0200	[thread overview]
Message-ID: <1598536.6uUjd689JJ@discus> (raw)
In-Reply-To: <20150709220609.GI10539@carfax.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]

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.
> 
>    btrfs subvolumes aren't block devices, so that rules out most of
> the usual approaches. However, there are two methods I've used which I
> can confirm will work well: NFS and 9p.
> 
>    NFS will work as a root filesystem, and will work with any
> host/guest, as long as there's a network connection between the two.
> 9p is, at least in theory, faster (particularly with virtio), but
> won't let you boot with the 9p device as your root FS. You'll need
> virtualiser support if you want to run a virtio 9p -- I know qemu/kvm
> supports this; I don't know if anything else supports it.


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.

Best,
Wolfgang

> 
>    You can probably use Samba/CIFS as well. It'll be slower than the
> virtualised 9p, and not be able to host a root filesystem. I haven't
> tried this one, because Samba and I get on like a house on fire(*).
> 
>    Hugo.
> 
> (*) Screaming, shouting, people running away, emergency services.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-07-09 22:13 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 [this message]
2015-07-17 18:12     ` Calvin Walton

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=1598536.6uUjd689JJ@discus \
    --to=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).