linux-btrfs.vger.kernel.org archive mirror
 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: Mon, 24 Aug 2015 23:50:50 -0700	[thread overview]
Message-ID: <20150825065050.GD20179@merlins.org> (raw)
In-Reply-To: <55DC0480.7080102@cn.fujitsu.com>

On Tue, Aug 25, 2015 at 02:00:32PM +0800, Qu Wenruo wrote:
> Thanks for all your work and patient Marc,
 
Haha, no problem, you're doing a lot more work than I am :)

> Good to know there is backup.
> But as there is no higher generation one, so I'd assume that's not a
> normal transaction id failure case.

Right.

> Personally, I'd like to try btrfsck with gen 39537(--tree-root 29687808),
> but that's all my personal curiosity.
> Although my curiosity is driving me from finding a clue how it's
> damaged to try to recover it.

I gave that a shot, same thing:
myth:~# btrfs check --repair --tree-root 29687808 /dev/mapper/crypt_sdd1
enabling repair mode
parent transid verify failed on 29687808 wanted 39538 found 39537
parent transid verify failed on 29687808 wanted 39538 found 39537
parent transid verify failed on 29687808 wanted 39538 found 39537
parent transid verify failed on 29687808 wanted 39538 found 39537
Ignoring transid failure
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.
btrfs[0x8066a83]
btrfs[0x8066ab4]
btrfs[0x80679d8]
btrfs[0x806b4f2]
btrfs[0x806b9ea]
btrfs[0x806c5f9]
btrfs(cmd_check+0x1088)[0x806ee26]
btrfs(main+0x153)[0x80557d6]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb75154d3]
btrfs[0x80557fc]

> If you think it's OK, then just wipe it, nobody has the right to
> disturb your sleep.
 
That's not a problem :) 
I signed up for bugs when using btrfs, and am happy to help with reports
and getting the tools improved with your help and others' where
possible.

> At least we got some clue here.
> Some parent nodes got corrupted with much higher and non-exists generation.

Right. So should I try to go back in time until it works, but the
previous level doesn't work either:

enabling repair mode
parent transid verify failed on 7312195813376 wanted 39538 found 39535
parent transid verify failed on 7312195813376 wanted 39538 found 39535
parent transid verify failed on 7312195813376 wanted 39538 found 39535
parent transid verify failed on 7312195813376 wanted 39538 found 39535
Ignoring transid failure
parent transid verify failed on 29687808 wanted 39524 found 39537
parent transid verify failed on 29687808 wanted 39524 found 39537
parent transid verify failed on 29687808 wanted 39524 found 39537
parent transid verify failed on 29687808 wanted 39524 found 39537
Ignoring transid failure
Checking filesystem on /dev/mapper/crypt_sdd1
UUID: 024ba4d0-dacb-438d-9f1b-eeb34083fe49
checking extents
cmds-check.c:3730: check_owner_ref: Assertion `rec->is_root` failed.
btrfs[0x8066a83]
btrfs[0x8066ab4]
btrfs[0x806acc4]
btrfs[0x806b9ea]
btrfs[0x806c5f9]
btrfs(cmd_check+0x1088)[0x806ee26]
btrfs(main+0x153)[0x80557d6]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb75104d3]
btrfs[0x80557fc]

Marc
-- 
"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-25  6:50 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
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 [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=20150825065050.GD20179@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).