From: Josef Bacik <josef@redhat.com>
To: Avi Kivity <avi.kivity@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Suddenly, a dead filesystem
Date: Tue, 23 Aug 2011 10:23:24 -0400 [thread overview]
Message-ID: <4E53B7DC.7020807@redhat.com> (raw)
In-Reply-To: <CAEbWaipxhyMf2VQRdfnpMcXwyf84YupLOm8hQRf4Q8wJu060ng@mail.gmail.com>
On 08/23/2011 10:15 AM, Avi Kivity wrote:
> I've been using btrfs for a while as my /home (converted from ext4;
> encrypted lvm) when it died on me. Mounting it crashes immediately,
> here's a log:
>
> [ 6.455721] ------------[ cut here ]------------
> [ 6.456117] kernel BUG at fs/btrfs/inode.c:4586!
> [ 6.456117] invalid opcode: 0000 [#1] SMP
> [ 6.456117] CPU 0
> [ 6.456117] Modules linked in: btrfs zlib_deflate libcrc32c
> [ 6.456117]
> [ 6.456117] Pid: 243, comm: mount Not tainted
> 2.6.40.3-0.fc15.x86_64 #1 Bochs Bochs
> [ 6.456117] RIP: 0010:[<ffffffffa0035642>] [<ffffffffa0035642>]
> btrfs_add_link+0x123/0x17c [btrfs]
> [ 6.456117] RSP: 0018:ffff880007ac9838 EFLAGS: 00010282
> [ 6.456117] RAX: 00000000ffffffef RBX: ffff880003ec3938 RCX: 0000000000000ed7
> [ 6.456117] RDX: 0000000000000ed6 RSI: 000060fff8e013b0 RDI: ffffea00000da3b0
> [ 6.456117] RBP: ffff880007ac98a8 R08: ffffffffa00123af R09: 0000000000000b23
> [ 6.456117] R10: 0000000000000b23 R11: 0000000000000002 R12: ffff880003ec3548
> [ 6.456117] R13: ffff880007863000 R14: 000000000000000d R15: ffff880007798500
> [ 6.456117] FS: 00007effe7241820(0000) GS:ffff880006e00000(0000)
> knlGS:0000000000000000
> [ 6.456117] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 6.456117] CR2: 00007effe62cc580 CR3: 0000000007b7c000 CR4: 00000000000006f0
> [ 6.456117] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 6.456117] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 6.456117] Process mount (pid: 243, threadinfo ffff880007ac8000,
> task ffff880002d40000)
> [ 6.456117] Stack:
> [ 6.456117] ffff880000000001 00000000000002cb ffff880007ac9878
> ffff880003e5d000
> [ 6.456117] 0000000000000000 3fff880002c5f000 0100000000002894
> 0000000000000000
> [ 6.456117] 0000000000001000 ffff880003e5a120 ffff880003ec3548
> ffff880007ac99c7
> [ 6.456117] Call Trace:
> [ 6.456117] [<ffffffffa005646e>] add_inode_ref+0x2e6/0x37c [btrfs]
> [ 6.456117] [<ffffffffa00493f6>] ? read_extent_buffer+0xc3/0xe3 [btrfs]
> [ 6.456117] [<ffffffffa0056e14>] replay_one_buffer+0x197/0x212 [btrfs]
> [ 6.456117] [<ffffffffa0054e94>] walk_down_log_tree+0x15a/0x2c1 [btrfs]
> [ 6.456117] [<ffffffffa005507a>] walk_log_tree+0x7f/0x19e [btrfs]
> [ 6.456117] [<ffffffff8123a8d9>] ? radix_tree_lookup+0xb/0xd
> [ 6.456117] [<ffffffffa0058148>] btrfs_recover_log_trees+0x28b/0x298 [btrfs]
> [ 6.456117] [<ffffffffa0056c7d>] ? replay_one_dir_item+0xbd/0xbd [btrfs]
> [ 6.456117] [<ffffffffa002a192>] open_ctree+0x10f1/0x13ff [btrfs]
> [ 6.456117] [<ffffffffa0010861>] btrfs_mount+0x233/0x496 [btrfs]
> [ 6.456117] [<ffffffff810f43fc>] ? pcpu_next_pop+0x3d/0x4a
> [ 6.456117] [<ffffffff810f54ca>] ? pcpu_alloc+0x7f7/0x833
> [ 6.456117] [<ffffffff81129b74>] mount_fs+0x69/0x155
> [ 6.456117] [<ffffffff810f5516>] ? __alloc_percpu+0x10/0x12
> [ 6.456117] [<ffffffff8113d905>] vfs_kern_mount+0x63/0x9d
> [ 6.456117] [<ffffffff8113e288>] do_kern_mount+0x4d/0xdf
> [ 6.456117] [<ffffffff8113f90d>] do_mount+0x63c/0x69f
> [ 6.456117] [<ffffffff810f1225>] ? memdup_user+0x55/0x7d
> [ 6.456117] [<ffffffff810f1288>] ? strndup_user+0x3b/0x51
> [ 6.456117] [<ffffffff8113fbf2>] sys_mount+0x88/0xc2
> [ 6.456117] [<ffffffff8148e182>] system_call_fastpath+0x16/0x1b
> [ 6.456117] Code: 89 f1 4c 89 fa 4c 89 ee 48 89 44 24 08 41 8b 04
> 24 66 c1 e8 0c 83 e0 0f 0f b6 80 78 eb 06 a0 89 04 24 e8 8c d5 fe ff
> 85 c0 74 02 <0f> 0b 45 01 f6 4d 63 f6 4c 03 b3 d0 00 00 00 4c 89 b3 d0
> 00 00
> [ 6.456117] RIP [<ffffffffa0035642>] btrfs_add_link+0x123/0x17c [btrfs]
> [ 6.456117] RSP <ffff880007ac9838>
> [ 6.592232] ---[ end trace 44b5956456a7dc01 ]---
>
> Tried btrfsck, immediate segfault.
>
> Both kernel and btrfsprogs are stock Fedora 15. I still have the
> logical volume and would like to recover it. Its fairly easy to try
> out things in a virtual machine, so if you have a patch you want me to
> try out, I'm here.
This is fixed upstream, I've sent the patch to -stable so hopefully it
will show up in fedora soon, but in the meantime can you try Linus's
tree and verify that it fixes it? Thanks,
Josef
next prev parent reply other threads:[~2011-08-23 14:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 14:15 Suddenly, a dead filesystem Avi Kivity
2011-08-23 14:23 ` Josef Bacik [this message]
2011-08-23 21:08 ` Avi Kivity
2011-09-30 21:40 ` Avi Kivity
2011-10-03 14:34 ` Josef Bacik
2011-10-03 15:12 ` Avi Kivity
2011-10-03 18:07 ` Avi Kivity
2011-10-04 14:39 ` Avi Kivity
2011-10-04 19:40 ` Avi Kivity
2011-10-04 19:41 ` Josef Bacik
2011-10-04 19:50 ` Avi Kivity
2011-10-04 20:01 ` Josef Bacik
2011-10-04 20:06 ` Avi Kivity
2011-08-23 14:27 ` Hugo Mills
2011-08-23 14:28 ` Hugo Mills
2011-08-23 22:22 ` Avi Kivity
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=4E53B7DC.7020807@redhat.com \
--to=josef@redhat.com \
--cc=avi.kivity@gmail.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