public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Josef Bacik <jbacik@fb.com>
Cc: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: send/receive locking
Date: Sat, 8 Mar 2014 22:00:27 +0000	[thread overview]
Message-ID: <20140308220027.GF6318@carfax.org.uk> (raw)
In-Reply-To: <usnory0eq5h626p5eaeeh4ki.1394315749442@email.android.com>

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

On Sat, Mar 08, 2014 at 09:55:50PM +0000, Josef Bacik wrote:
> Hey Hugo will you try the danger branch on btrfs-next, Wang changed the locking a bit.  Thanks,

   Sure. I'll build a kernel tonight and report tomorrow. I'm not sure
how repeatable the problem is, though. I'll see if I can quantify
that, too.

   Hugo.

> Josef
> 
> Hugo Mills <hugo@carfax.org.uk> wrote:
> 
> 
>    Is there anything that can be done about the issues of btrfs send
> blocking? I've been writing a backup script (slowly), and several
> times I've managed to hit a situation where large chunks of the
> machine grind to a complete halt in D state because the backup script
> has jammed up.
> 
>    Now, I'm aware that you can't send and receive to the same
> filesystem at the same time, and that's a restriction I can live with.
> However, having things that aren't related to the backup process
> suddenly stop working because the backup script is trying to log its
> progress to the same FS it's backing up is... umm... somewhat vexing,
> to say the least.
> 
>    Is this a truly fundamental property of send/receive, or is there
> likely to be a simple(ish) solution?
> 
>    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
   --- Well, you don't get to be a kernel hacker simply by looking ---   
                    good in Speedos. -- Rusty Russell                    

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

  reply	other threads:[~2014-03-08 22:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 15:18 3.14.0-rc3: btrfs send/receive blocks btrfs IO on other devices (near deadlocks) Marc MERLIN
2014-03-10 10:39 ` [PATCH] Btrfs-progs: fsck: disable --init-extent-tree option when using snapshots Wang Shilong
2014-03-10 12:12   ` Shilong Wang
2014-03-10 15:50     ` Josef Bacik
2014-03-11  1:23       ` Wang Shilong
2014-03-08 21:53         ` send/receive locking Hugo Mills
2014-03-08 21:55           ` Josef Bacik
2014-03-08 22:00             ` Hugo Mills [this message]
2014-03-08 22:02               ` Josef Bacik
2014-03-08 22:16                 ` Hugo Mills
2014-03-09 16:43                   ` Hugo Mills
2014-03-10 22:28                     ` Hugo Mills
2014-03-14  2:19           ` Marc MERLIN
2014-03-14 13:36         ` [PATCH] Btrfs-progs: fsck: disable --init-extent-tree option when using snapshots Wang Shilong
2014-03-14 14:36           ` Josef Bacik
2014-03-17 12:21             ` Shilong Wang
2014-03-14  1:48 ` 3.14.0-rc3: btrfs send/receive blocks btrfs IO on other devices (near deadlocks) Marc MERLIN
2014-03-14  4:54   ` Duncan
2014-03-14 14:42 ` Josef Bacik

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=20140308220027.GF6318@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=jbacik@fb.com \
    --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