linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Wyzer <john.wyzer@gmx.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfsck segmentation fault + trace
Date: Wed, 16 Jun 2010 17:52:40 +0200	[thread overview]
Message-ID: <4C18F348.80509@gmx.de> (raw)

I tried 2.6.35-rc3 and got error messages during the boot process about not being able
to dirty inodes and no space left on device.

2.6.34.y runs fine and df -h shows
rootfs                296G  255G   39G  87% /

I reverted back to 2.6.34 and gave btrfsck a try resulting in a segmentation fault.

# btrfsck /dev/mapper/root 
parent transid verify failed on 217995780096 wanted 155238 found 155234
btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed.
Aborted (core dumped)


Core was generated by `btrfsck /dev/mapper/root'.
Program terminated with signal 6, Aborted.
#0  0xffffe424 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb76c2751 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0xb76c5b82 in *__GI_abort () at abort.c:92
#3  0xb76bb8b8 in *__GI___assert_fail (assertion=0x8062dc7 "!(!root->node)", file=0x8062d2d "disk-io.c", line=416, 
    function=0x8062fe0 "find_and_setup_root") at assert.c:81
#4  0x080525bb in find_and_setup_root (tree_root=0x9852008, fs_info=<value optimized out>, objectid=2, root=0x9852178)
    at disk-io.c:416
#5  0x08052dcd in open_ctree_fd (fp=3, path=0xbfd984f9 "/dev/mapper/root", sb_bytenr=0, writes=0) at disk-io.c:740
#6  0x0805303d in open_ctree (filename=0xbfd984f9 "/dev/mapper/root", sb_bytenr=0, writes=0) at disk-io.c:587
#7  0x0804d36b in main (ac=2, av=0xbfd98344) at btrfsck.c:2824
(gdb) 

Hope that helps in any way :-)
Best regards.

             reply	other threads:[~2010-06-16 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 15:52 John Wyzer [this message]
2010-06-16 16:31 ` btrfsck segmentation fault + trace Chris Mason
2010-06-16 16:35   ` John Wyzer
2010-06-16 17:29     ` Chris Mason
2010-06-16 20:25       ` John Wyzer
2010-06-16 22:45         ` Yan, Zheng 
2010-06-16 23:26           ` John Wyzer
2010-06-16 23:36             ` Yan, Zheng 

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=4C18F348.80509@gmx.de \
    --to=john.wyzer@gmx.de \
    --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;
as well as URLs for NNTP newsgroup(s).