Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Tamas Papp <tompos@martos.bme.hu>
To: linux-btrfs@vger.kernel.org
Subject: Re: open_ctree failed
Date: Tue, 24 Jun 2014 09:52:15 +0200	[thread overview]
Message-ID: <53A92E2F.7090401@martos.bme.hu> (raw)
In-Reply-To: <53A70E0C.6000602@martos.bme.hu>


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



Thanks for the help!


tamas

  reply	other threads:[~2014-06-24  7:52 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 [this message]
2014-06-24 16:37           ` Chris Murphy
2014-06-25 13:09             ` Tamas Papp
2014-06-25 13:31               ` Tamas Papp

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=53A92E2F.7090401@martos.bme.hu \
    --to=tompos@martos.bme.hu \
    --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