From: Tamas Papp <tompos@martos.bme.hu>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: open_ctree failed
Date: Wed, 25 Jun 2014 15:31:22 +0200 [thread overview]
Message-ID: <53AACF2A.7000200@martos.bme.hu> (raw)
In-Reply-To: <53AACA21.5060504@martos.bme.hu>
On 06/25/2014 03:09 PM, Tamas Papp wrote:
>
> On 06/24/2014 06:37 PM, Chris Murphy wrote:
>> On Jun 24, 2014, at 1:52 AM, Tamas Papp <tompos@martos.bme.hu> wrote:
>>
>>> On 06/22/2014 07:10 PM, Tamas Papp wrote:
>>>> On 06/20/2014 02:04 AM, George Mitchell wrote:
>>>>> Hello Tamas,
>>>>>
>>>>> I think it would help to provide more information than what you
>>>>> have posted. "open_ctree" can cover a lot of territory.
>>>>>
>>>>> 1) I may be missing something, but I see no attachment. I am not
>>>>> sure the mailing list can handle attachments?
>>>> Indeed, thanks!
>>>>
>>>> chunk recover:
>>>> http://pastebin.com/raw.php?i=01ZdbCDq
>>>>
>>>> debug tree:
>>>> http://pastebin.com/raw.php?i=LgKgEhiC
>>>>
>>>> dmesg:
>>>> http://pastebin.com/raw.php?i=zZ5zVxue
>>>>
>>>> dmidecode:
>>>> http://pastebin.com/raw.php?i=zZ5zVxue
>>>>
>>>> find root:
>>>> http://pastebin.com/raw.php?i=zWdn56tR
>>>>
>>>> show super:
>>>> http://pastebin.com/raw.php?i=unqZECJ3
>>>>
>>>> super recover:
>>>> http://pastebin.com/raw.php?i=y7fKtn3M
>>>>
>>>>> 2) I think it would help to include some sort of brief narrative
>>>>> as to what you are trying to do when you encounter the open_ctree
>>>>> failure.
>>>> I'm just trying to mount the partition:
>>>>
>>>> mount -t btrfs /dev/sda4 /1
>>>>
>>> dmesg after -o recovery:
>>>
>>> http://pastebin.com/raw.php?i=VAG9msx2
>> super-recover says supers are good, btrfs-find-tree finds tree root,
>> but chunk-recover fails.
>>
>> Please post the result from smartctl -x <dev>
>>
>> I'd make sure you're on kernel 3.14 at the oldest, and same for
>> btrfs-progs. Currently you're on v.3.12. And then also post the
>> result of btrfs check (without --repair).
>
> smartctl -x:
>
> http://pastebin.com/raw.php?i=S3eaCb8b
>
>
> The machine was running 3.15rcX, when it failed. Unfortunately I have
> only a live system now with this kernel versionI. I tried with the
> latest btrfs-progs from git with no success.
>
> btrfs check (with v3.12):
>
> Check tree block failed, want=325877760, have=0
> Check tree block failed, want=325877760, have=0
> Check tree block failed, want=325877760, have=0
> read block failed check_tree_block
> Couldn't setup extent tree
> Critical roots corrupted, unable to fsck the FS
> Checking filesystem on /dev/sda4
> UUID: 7cf95491-8ec6-48a2-b4c4-4b80650d169a
>
With latest from git (3.14.2):
Check tree block failed, want=325877760, have=0
Check tree block failed, want=325877760, have=0
Check tree block failed, want=325877760, have=0
read block failed check_tree_block
Couldn't setup extent tree
Check tree block failed, want=324567040, have=0
Check tree block failed, want=324567040, have=0
Check tree block failed, want=324567040, have=0
read block failed check_tree_block
Couldn't setup csum tree
Check tree block failed, want=326631424, have=0
Check tree block failed, want=326631424, have=0
Check tree block failed, want=326631424, have=0
read block failed check_tree_block
Couldn't setup log root tree
Critical roots corrupted, unable to fsck the FS
Segmentation fault (core dumped)
tamaas
prev parent reply other threads:[~2014-06-25 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <539EF06A.4080803@martos.bme.hu>
2014-06-16 14:02 ` open_ctree failed Tamas Papp
2014-06-19 21:50 ` Tamas Papp
2014-06-20 0:04 ` George Mitchell
2014-06-22 17:10 ` Tamas Papp
2014-06-24 7:52 ` Tamas Papp
2014-06-24 16:37 ` Chris Murphy
2014-06-25 13:09 ` Tamas Papp
2014-06-25 13:31 ` Tamas Papp [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=53AACF2A.7000200@martos.bme.hu \
--to=tompos@martos.bme.hu \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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.