All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: BJ Quinn <bj@placs.net>
Cc: linux-btrfs@vger.kernel.org, psusi@cfl.rr.com,
	Freddie Cash <fjwcash@gmail.com>
Subject: Re: Fwd: Cloning a Btrfs partition
Date: Mon, 29 Jul 2013 10:21:51 +0200	[thread overview]
Message-ID: <51F6261F.204@jan-o-sch.net> (raw)
In-Reply-To: <24149367.8309.1374769963900.JavaMail.root@mail.placs.net>

Hi BJ,

[original message rewrapped]

On Thu, July 25, 2013 at 18:32 (+0200), BJ Quinn wrote:
> (Apologies for the double post -- forgot to send as plain text the first time
> around, so the list rejected it.)
> 
> I see that there's now a btrfs send / receive and I've tried using it, but
> I'm getting the oops I've pasted below, after which the FS becomes
> unresponsive (no I/O to the drive, no CPU usage, but all attempts to access
> the FS results in a hang). I have an internal drive (single drive) that
> contains 82GB of compressed data with a couple hundred snapshots. I tried
> taking the first snapshot and making a read only copy (btrfs subvolume
> snapshot -r) and then I connected an external USB drive and ran btrfs send /
> receive to that external drive. It starts working and gets a couple of GB in
> (I'd expect the first snapshot to be about 20GB) and then gets the following
> error. I had to use the latest copy of btrfs-progs from git, because the
> package installed on my system (btrfs-progs-0.20-0.2.git91d9eec) simply
> returned "invalid argument" when trying to run btrfs send / receive. Thanks
> in advance for any info you may have.

The problem has been introduced with rbtree ulists in 3.10, commit

    Btrfs: add a rb_tree to improve performance of ulist search

You should be safe to revert that commit, it's a performance optimization
attempt. Alternatively, you can apply the published fix

    Btrfs: fix crash regarding to ulist_add_merge

It has not made it into 3.10 stable or 3.11, yet, but is contained in Josef's
btrfs-next

    git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git

Thanks,
-Jan

  reply	other threads:[~2013-07-29  8:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9213759.7842.1374769206286.JavaMail.root@mail.placs.net>
2013-07-25 16:32 ` Fwd: Cloning a Btrfs partition BJ Quinn
2013-07-29  8:21   ` Jan Schmidt [this message]
2013-07-29 15:32     ` BJ Quinn
2013-07-30 10:28       ` Jan Schmidt
2013-08-19 20:45         ` BJ Quinn
2013-08-20  9:59           ` Xavier Bassery
2013-08-20 15:43             ` BJ Quinn
2013-11-02  0:28               ` kernel BUG at fs/btrfs/ctree.c:2964! BJ Quinn
2013-11-02  1:34                 ` Josef Bacik
2013-11-07 23:35                   ` Ilari Stenroth

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=51F6261F.204@jan-o-sch.net \
    --to=list.btrfs@jan-o-sch.net \
    --cc=bj@placs.net \
    --cc=fjwcash@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=psusi@cfl.rr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.