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: Fri, 10 Feb 2012 16:27:49 -0500 [thread overview]
Message-ID: <20120210212749.GR8384@shiny> (raw)
In-Reply-To: <CAAE6i0h+E0vQ4D6gr7MQiwS00hnQGk5R7ubkRa00NdkoaNxcNA@mail.gmail.com>
On Thu, Feb 09, 2012 at 06:54:42PM -0600, Chester wrote:
> Output for btrfs-debug-tree for that specific block in dmesg
>
> And available here ( http://pastebin.com/AgdvS5JM ) in case the lines
> wrap and look ugly
>
> leaf 653297209344 items 43 free space 673 generation 332442 owner 2
> fs uuid 0f5b2f4f-1aa0-4e6f-b904-e5b4d4588144
> chunk uuid 27536f0d-993b-4da3-85eb-1c9b08c435cb
> item 7 key (653284831232 EXTENT_ITEM 4096) itemoff 3551 itemsize 51
> extent refs 1 gen 332218 flags 2
> tree block key (654686961664 a8 4096) level 0
> tree block backref root 2
> item 8 key (653284818944 EXTENT_ITEM 4096) itemoff 3500 itemsize 51
> extent refs 1 gen 332218 flags 2
> tree block key (654687121408 a8 4096) level 0
> tree block backref root 2
Ok, its worth pointing out that you're just one bit away from proper
ordering here. While I'm testing out this code to fix key ordering,
could you please run memtest86 on your machine?
The other fields all look correct.
-chris
next prev parent reply other threads:[~2012-02-10 21:27 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
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 [this message]
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=20120210212749.GR8384@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.