From: Chris Mason <chris.mason@oracle.com>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs unmountable after failed suspend
Date: Wed, 8 Feb 2012 07:55:36 -0500 [thread overview]
Message-ID: <20120208125536.GI16796@shiny> (raw)
In-Reply-To: <CAAE6i0hXA7rzZ=VCnezfyHQFn=+UcfrmUsfR-GQZcgvxFW+qJQ@mail.gmail.com>
On Tue, Feb 07, 2012 at 06:10:15PM -0600, Chester wrote:
> This is dmesg mounted with -o ro,recovery
> [ 20.957392] exe used greatest stack depth: 4920 bytes left
> [ 145.340317] device label BtrfsLinux devid 1 transid 332442 /dev/sda6
> [ 145.341702] btrfs: enabling auto recovery
> [ 145.341803] btrfs: disk space caching is enabled
> [ 152.457967] btrfs: corrupt leaf, bad key order:
> block=653297209344,root=1, slot=7
> [ 152.487933] btrfs: corrupt leaf, bad key order:
> block=653297209344,root=1, slot=7
> [ 152.488326] ------------[ cut here ]------------
> [ 152.488549] kernel BUG at fs/btrfs/extent-tree.c:5797!
Well, this isn't good. If you can run btrfs-zero-log it'll get past
this part, but I'd suggest a fsck run to see if there are other
corrupted blocks.
Bad key ordering is usually from memory corruption, so this block
probably isn't alone.
-chris
next prev parent reply other threads:[~2012-02-08 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 22:58 btrfs unmountable after failed suspend Chester
2012-02-07 23:22 ` Chester
2012-02-08 0:10 ` Chester
2012-02-08 12:55 ` Chris Mason [this message]
2012-02-08 19:22 ` Chester
2012-02-08 20:26 ` Chris Mason
2012-02-08 20:46 ` Chester
2012-02-09 0:17 ` Chester
2012-02-10 0:54 ` Chester
2012-02-10 1:32 ` Chris Mason
2012-02-10 1:40 ` Chester
2012-02-10 21:27 ` Chris Mason
2012-02-11 21:42 ` Chester
2012-03-31 2:32 ` Chester
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=20120208125536.GI16796@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@gmail.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