public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel BUG: btrfs send - Incremental backup
Date: Wed, 12 Mar 2014 09:20:09 +0100	[thread overview]
Message-ID: <1534308.rS2sq7rkIX@tethys> (raw)
In-Reply-To: <531F4419.8010109@fb.com>

Hi Josef,

I'm afraid I will not have the time to perform the kernel compilations and 
tests you request in the coming days. I'm sorry but I will really be 120% 
overloaded already...

Kind regards.

Le mardi 11 mars 2014 13:12:57 Josef Bacik a écrit :
> Well that's odd, I can't think of how this would happen.  Can pull
> down btrfs-next and run that and verify you still hit the BUG_ON?  If
> you do please apply this patch and re-run and reply with the dmesg.
> 
> http://paste.fedoraproject.org/84393/55775013
> 
> This will spit out something like this
> 
> cur_ino=<NUMBER>, cmp_key objectid=<OTHER NUMBER>
> 
> then I need you to unmount your fs and run
> 
> btrfs-debug-tree /dev/whatever > blah.txt
> 
> You have about 1.5 gig of metadata so that is going to take a while.
> Once that is done you want to go through blah.txt and look for
> 
> item <number> key (<OTHER NUMBER FROM ABOVE> EXTENT_DATA <number>)
> 
> You need to find all of these entries and copy them down, an example
> output looks like this
> 
> item 1 key (286 EXTENT_DATA 577536) itemoff 3889 itemsize 53
>         extent data disk byte 12763136 nr 4096
>         extent data offset 0 nr 4096 ram 4096
>         extent compression 0
> 
> That is what I'm looking for, you will have multiple of these.  Thanks,
> 
> Josef

-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E


  reply	other threads:[~2014-03-12  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08  7:35 Kernel BUG: btrfs send - Incremental backup Swâmi Petaramesh
2014-03-10  2:16 ` quwenruo
2014-03-10  7:25   ` Swâmi Petaramesh
2014-03-10  7:34     ` quwenruo
2014-03-10  8:30       ` Swâmi Petaramesh
2014-03-11 17:12 ` Josef Bacik
2014-03-12  8:20   ` Swâmi Petaramesh [this message]
2014-03-12 17:07     ` 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=1534308.rS2sq7rkIX@tethys \
    --to=swami@petaramesh.org \
    --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