From: Chris Mason <chris.mason@oracle.com>
To: John Wyzer <john.wyzer@gmx.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck segmentation fault + trace
Date: Wed, 16 Jun 2010 12:31:09 -0400 [thread overview]
Message-ID: <20100616163109.GX27466@think> (raw)
In-Reply-To: <4C18F348.80509@gmx.de>
On Wed, Jun 16, 2010 at 05:52:40PM +0200, John Wyzer wrote:
> 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.
Is 2.6.34 working normally?
>
> 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)
This shows a bad metadata block, basically a missed write. It sounds
like something has gone wrong with this system.
-chris
next prev parent reply other threads:[~2010-06-16 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:52 btrfsck segmentation fault + trace John Wyzer
2010-06-16 16:31 ` Chris Mason [this message]
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=20100616163109.GX27466@think \
--to=chris.mason@oracle.com \
--cc=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).