All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: Josef Bacik <jbacik@fb.com>,
	dsterba@suse.com, clm@fb.com, linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:8113! (4.1.3 kernel)
Date: Sat, 22 Aug 2015 07:37:46 -0700	[thread overview]
Message-ID: <20150822143746.GG5602@merlins.org> (raw)
In-Reply-To: <20150817144904.GT29259@merlins.org>

On Mon, Aug 17, 2015 at 07:49:04AM -0700, Marc MERLIN wrote:
> On Mon, Aug 17, 2015 at 10:01:16AM +0800, Qu Wenruo wrote:
> > Hi Marc,
>  
> Hi Qu, thanks for your answer and looking at this.
> 
> > Did btrfs-debug-tree also has the crash?
> > 
> > If not, would you please attach the output if it doesn't contain
> > classified data.
  
Do you need anything else before I wipe the filesystem and start over?

1) kernel is fixed not to crash
2) btrfs check --repair segfaults
3) btrfs-debug-tree ends with assert

Thanks,
Marc

> Sure thing:
> btrfs-debug-tree /dev/mapper/crypt_sdd1 > /tmp/tree.out
> parent transid verify failed on 2968115101696 wanted 34855 found 39533
> parent transid verify failed on 2968115101696 wanted 34855 found 39533
> parent transid verify failed on 2968115101696 wanted 34855 found 39533
> parent transid verify failed on 2968115101696 wanted 34855 found 39533
> Ignoring transid failure
> parent transid verify failed on 2968115134464 wanted 34855 found 39533
> parent transid verify failed on 2968115134464 wanted 34855 found 39533
> parent transid verify failed on 2968115134464 wanted 34855 found 39533
> parent transid verify failed on 2968115134464 wanted 34855 found 39533
> Ignoring transid failure
> parent transid verify failed on 2968115150848 wanted 34855 found 39533
> parent transid verify failed on 2968115150848 wanted 34855 found 39533
> parent transid verify failed on 2968115150848 wanted 34855 found 39533
> parent transid verify failed on 2968115150848 wanted 34855 found 39533
> Ignoring transid failure
> parent transid verify failed on 2968115691520 wanted 34855 found 39533
> parent transid verify failed on 2968115691520 wanted 34855 found 39533
> parent transid verify failed on 2968115691520 wanted 34855 found 39533
> parent transid verify failed on 2968115691520 wanted 34855 found 39533
> Ignoring transid failure
> parent transid verify failed on 1291597152256 wanted 35830 found 39530
> parent transid verify failed on 1291597152256 wanted 35830 found 39530
> parent transid verify failed on 1291597152256 wanted 35830 found 39530
> parent transid verify failed on 1291597152256 wanted 35830 found 39530
> Ignoring transid failure
> parent transid verify failed on 2968116592640 wanted 34855 found 39533
> parent transid verify failed on 2968116592640 wanted 34855 found 39533
> parent transid verify failed on 2968116592640 wanted 34855 found 39533
> parent transid verify failed on 2968116592640 wanted 34855 found 39533
> Ignoring transid failure
> parent transid verify failed on 2968116609024 wanted 34855 found 39533
> parent transid verify failed on 2968116609024 wanted 34855 found 39533
> parent transid verify failed on 2968116609024 wanted 34855 found 39533
> parent transid verify failed on 2968116609024 wanted 34855 found 39533
> Ignoring transid failure
> print-tree.c:1094: btrfs_print_tree: Assertion failed.
> btrfs-debug-tree[0x805ce93]
> btrfs-debug-tree(btrfs_print_tree+0x26d)[0x805eb51]
> btrfs-debug-tree(btrfs_print_tree+0x279)[0x805eb5d]
> btrfs-debug-tree(main+0x8b5)[0x804dfb7]
> /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb757c4d3]
> btrfs-debug-tree[0x804e221]
> 
> Do you want the actual output?
> (it's 1.1GB uncompressed)
> 
> Marc
> 
> 
> > Thanks,
> > Qu
> > 
> > Marc MERLIN wrote on 2015/08/12 10:19 -0700:
> > >On Wed, Aug 12, 2015 at 12:18:45PM -0400, Josef Bacik wrote:
> > >>Going to need more info to figure this one out
> > >
> > >Thanks for the patch, here's the output:
> > >enabling repair mode
> > >Checking filesystem on /dev/mapper/crypt_sdd1
> > >UUID: 024ba4d0-dacb-438d-9f1b-eeb34083fe49
> > >checking extents
> > >wtf, parent 575708413952 <<<<<<
> > >cmds-check.c:4488: add_data_backref: Assertion `back->bytes != max_size` failed.
> > >/tmp/btrfs[0x8066a83]
> > >/tmp/btrfs[0x8066ab4]
> > >/tmp/btrfs[0x80679d8]
> > >/tmp/btrfs[0x806b4f2]
> > >/tmp/btrfs[0x806b9ea]
> > >/tmp/btrfs[0x806c5f9]
> > >/tmp/btrfs(cmd_check+0x1088)[0x806ee26]
> > >/tmp/btrfs(main+0x153)[0x80557d6]
> > >/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb75a54d3]
> > >/tmp/btrfs[0x80557fc]
> > >
> > >Marc
> > >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 
> -- 
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
> Microsoft is to operating systems ....
>                                       .... what McDonalds is to gourmet cooking
> Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2015-08-22 14:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 21:21 btrfs check --repair crash, and btrfs-cleaner crash Marc MERLIN
2015-07-10 13:43 ` Btrfs progs release 4.1.1 David Sterba
2015-07-12  1:02   ` Marc MERLIN
2015-07-23 11:55     ` David Sterba
2015-07-24 16:24       ` Marc MERLIN
2015-08-03  3:51         ` kernel BUG at fs/btrfs/extent-tree.c:8113! (4.1.3 kernel) Marc MERLIN
2015-08-11  5:07           ` Marc MERLIN
2015-08-11 15:40             ` Josef Bacik
2015-08-12 14:47               ` Marc MERLIN
2015-08-12 15:15                 ` Josef Bacik
2015-08-12 16:09                   ` Marc MERLIN
2015-08-12 16:18                     ` Josef Bacik
2015-08-12 17:19                       ` Marc MERLIN
2015-08-17  2:01                         ` Qu Wenruo
2015-08-17 14:49                           ` Marc MERLIN
2015-08-22 14:37                             ` Marc MERLIN [this message]
2015-08-24  1:10                               ` Qu Wenruo
2015-08-24  4:28                                 ` Marc MERLIN
2015-08-24  5:11                                   ` Qu Wenruo
2015-08-24 14:10                                     ` Marc MERLIN
2015-08-25  0:26                                       ` Qu Wenruo
2015-08-25  2:51                                       ` Qu Wenruo
2015-08-25  5:28                                         ` Marc MERLIN
2015-08-25  6:00                                           ` Qu Wenruo
2015-08-25  6:50                                             ` Marc MERLIN

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=20150822143746.GG5602@merlins.org \
    --to=marc@merlins.org \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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.