linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Noret <tnoret@yahoo.fr>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/tree-log.c:820!
Date: Sun, 05 Jun 2011 23:33:39 +0200	[thread overview]
Message-ID: <4DEBF633.1010109@yahoo.fr> (raw)
In-Reply-To: <BANLkTim3_bu8HMYrimQZ3E50yD8R1cO3QA@mail.gmail.com>

Le 05/06/2011 22:58, Fajar A. Nugraha a =E9crit :
> On Mon, Jun 6, 2011 at 1:34 AM, Thierry Noret<tnoret@yahoo.fr>  wrote=
:
>> Hello,
>>
>> Since my computer has switch off with hard reset, I can't mount my h=
ome
>> directory.
>> / is btrfs too and there is no problem
>> Kernel-2.6.38-R6
>> I've try with 2.6.39 and same problem
>>
>> Thanks
>>
>> T.Noret
>>
>> ------------[ cut here ]------------
>> kernel BUG at fs/btrfs/tree-log.c:820!
>> invalid opcode: 0000 [#1] PREEMPT SMP
>> last sysfs file:
>> /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block=
/sda/sda1/alignment_offset
>> CPU 7
>> Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek fglrx(P)
>> snd_hda_intel snd_hda_codec ath9k ath9k_common xhci_hcd ath9k_hw uvc=
video
>> videodev i2c_i801 i7core_edac v4l2_compat_ioctl32 asus_laptop atl1c
>> snd_hwdep snd_pcm snd_timer snd snd_page_alloc ath sparse_keymap
>> Pid: 1821, comm: mount Tainted: P            2.6.38-gentoo-r6 #1 ASU=
STeK
>> Computer Inc.         N61Jq/N61Jq
>> RIP: 0010:[<ffffffff8120726f>]  [<ffffffff8120726f>]
>> add_inode_ref+0x4af/0x4c0
>> RSP: 0018:ffff88013d86d8e8  EFLAGS: 00010246
>> RAX: 0000000000000000 RBX: 0000000000000002 RCX: 00000000fffb9a44
>> RDX: ffffffff81660240 RSI: ffffffff811d3540 RDI: ffff88013ccc25a0
>> RBP: 0000000000000097 R08: fea53429e2fd5403 R09: 0000000000000001
>> R10: 0000000000000000 R11: 0000000000000001 R12: ffff88013d86db88
>> R13: ffff88013fbe7ee0 R14: 0000000000000009 R15: ffff88013d86da08
>> FS:  00007fee197f1740(0000) GS:ffff8800bb3c0000(0000) knlGS:00000000=
00000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>> CR2: 00007feb06b2a0f0 CR3: 000000013da18000 CR4: 00000000000006e0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> Process mount (pid: 1821, threadinfo ffff88013d86c000, task
>> ffff88013d01f580)
>> Stack:
>> ffff88013d86d8e8 000000003d86d8e8 ffffffff811cb0f0 0000000000000000
>> ffff88013e7af800 ffff88013f893090 ffff88013e7ae800 ffff88013fbe7ee0
>> 0000000000000000 ffff88013ccc28f8 ffff88013f930810 ffff88013fbe7ee0
>> Call Trace:
>> [<ffffffff811cb0f0>] ? btree_get_extent+0x0/0x1c0
>> [<ffffffff811f7303>] ? read_extent_buffer+0xc3/0x1d0
>> [<ffffffff81209340>] ? replay_one_buffer+0x2d0/0x3a0
>> [<ffffffff8120824d>] ? walk_down_log_tree+0x37d/0x530
>> [<ffffffff81208503>] ? walk_log_tree+0x103/0x280
>> [<ffffffff8120b218>] ? btrfs_recover_log_trees+0x228/0x310
>> [<ffffffff81209070>] ? replay_one_buffer+0x0/0x3a0
>> [<ffffffff811cf554>] ? open_ctree+0x1254/0x15e0
>> [<ffffffff8127ac86>] ? vsnprintf+0x496/0x650
>> [<ffffffff811ac810>] ? btrfs_set_super+0x0/0x20
>> [<ffffffff811accfe>] ? btrfs_mount+0x38e/0x4d0
>> [<ffffffff810e704e>] ? vfs_kern_mount+0x6e/0x1d0
>> [<ffffffff811001ee>] ? get_fs_type+0x3e/0xd0
>> [<ffffffff810e7223>] ? do_kern_mount+0x53/0x120
>> [<ffffffff81103746>] ? do_mount+0x456/0x820
>> [<ffffffff810bea8f>] ? memdup_user+0x3f/0x80
>> [<ffffffff81103eca>] ? sys_mount+0x9a/0xf0
>> [<ffffffff81002dfb>] ? system_call_fastpath+0x16/0x1b
>> Code: b8 67 ef ff 48 8b 7c 24 68 e8 ae 67 ef ff 31 c0 48 81 c4 98 00=
 00 00
>> 5b 5d 41 5c 41 5d 41 5e 41 5f c3 b8 fe ff ff ff eb e7 0f 0b<0f>  0b =
0f 0b 0f
>> 0b 0f 0b 0f 0b 0f 0b 0f 1f 44 00 00 41 57 41 56
>> RIP  [<ffffffff8120726f>] add_inode_ref+0x4af/0x4c0
>> RSP<ffff88013d86d8e8>
>> ---[ end trace a525b4b72005f64a ]---
>>
>
> Do you have some lines like this on syslog/dmesg as well?
>
> [    9.564301] parent transid verify failed on 44040192 wanted 38240 =
found 32526
>
> If yes, some options you coud try:
> - try "btrfsck -s1 /dev/sda1" (or whatever your /home block device is=
)
> to try alternate superblock. If it finish without errors, you might b=
e
> able to use btrfs-select-super
> - try btrfs-zero-log
>
> btrfs-select-super and btrfs-zero-log isn't compiled by default, so
> you need to grab the sources and compile them with "make
> btrfs-select-super" and "make btrfs-zero-log"
>
Nothing like this in my dmesg and the command doesn't work.
It return "Could not check mount status: Unknow error"
I've upgrade btrfs-progs from git

Before the bug there is

btrfs: use lzo compression
unlinked 1 orphans
device fsid 6b403b670b1ed576-50d13d7dbfc6b4a4 devid 1 transid 12386=20
/dev/sda4

If it can help here is my entire dmesg
http://pastebin.com/e16ttHyM

Thanks
--
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

      reply	other threads:[~2011-06-05 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05 18:34 kernel BUG at fs/btrfs/tree-log.c:820! Thierry Noret
2011-06-05 20:58 ` Fajar A. Nugraha
2011-06-05 21:33   ` Thierry Noret [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=4DEBF633.1010109@yahoo.fr \
    --to=tnoret@yahoo.fr \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    /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).