Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Lists <lists@benjamindsmith.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS send/receive limitations
Date: Fri, 4 Apr 2014 18:59:25 +0100	[thread overview]
Message-ID: <20140404175924.GS7442@carfax.org.uk> (raw)
In-Reply-To: <533EE2BD.7060608@benjamindsmith.com>

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

On Fri, Apr 04, 2014 at 09:50:05AM -0700, Lists wrote:
> I read recently that you can't send/receive concurrent streams on the same
> filesystem, which begs the question of what is meant by a "filesystem". Is
> that to say that you can't send/receive snapshots on different subvolumes to
> the same "root filesystem"? Or that you can't send/receive multiple
> snapshots on the same subvolume? Can you send/receive a snapshot or
> subvolume to the same root filesystem?

   The restriction was on the same *filesystem* as a whole: there was
a global lock on the whole FS, which could cause deadlocks with send
and receive both accessing the same FS (any subvolumes). I don't
recall hearing about problems with two sends from different subvols on
the same FS, but that might just be because I wasn't paying attention.
:)

   I think those restrictions are gone now, in some patch in the
pipeline. Possibly for 3.15 -- I'm not sure if the patches made it
into 3.14.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
     --- Gomez, darling, don't torture yourself.  That's my job. ---     

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      reply	other threads:[~2014-04-04 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 16:50 BTRFS send/receive limitations Lists
2014-04-04 17:59 ` Hugo Mills [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=20140404175924.GS7442@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@benjamindsmith.com \
    /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