From: cwillu <cwillu@cwillu.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: "open_ctree failed", unable to mount the fs
Date: Fri, 7 Jan 2011 13:47:17 -0600 [thread overview]
Message-ID: <AANLkTint9312XUw3LqHWTyP5_LQTaUgRzXE8KfBdbYta@mail.gmail.com> (raw)
In-Reply-To: <4D276899.7000702@wpkg.org>
On Fri, Jan 7, 2011 at 1:25 PM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> The forthcoming[1] btrfsck tool should handle that particular
>> error, I believe.
>
> I noticed a similar problem was discussed here, with a solution:
>
> http://www.spinics.net/lists/linux-btrfs/msg07572.html
>
>
> where a "btrfs-selects-super" was used:
>
>> git clone
>> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
>> next
>>
>> (or git pull into your existing checkout)
>>
>> Then
>>
>> make btrfs-select-super
>> ./btrfs-selects-super -s 1 /dev/xxx
>>
>> After this you'll want to do a full backup and make sure things are
>> working properly.
>
>
> However, I don't see the tool when I clone the latest git - am I missing something?
It's not built by the makefile by default; "make btrfs-select-super"
as stated above will make it.
next prev parent reply other threads:[~2011-01-07 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:25 "open_ctree failed", unable to mount the fs Tomasz Chmielewski
2011-01-07 19:47 ` cwillu [this message]
[not found] ` <AANLkTik3GZVTwco+4PNFriB0+t_U=e+dH0UOgK_3P9D5@mail.gmail.com>
2011-01-07 20:01 ` Tomasz Chmielewski
2011-01-07 20:18 ` cwillu
2011-01-07 20:44 ` Tomasz Chmielewski
[not found] <S1750921Ab1CIXPz/20110309231555Z+1799@vger.kernel.org>
2011-03-09 23:28 ` Tomáš Thiemel
-- strict thread matches above, loose matches on Subject: below --
2011-01-07 19:01 Tomasz Chmielewski
2011-01-07 19:09 ` Hugo Mills
2011-01-07 20:02 ` 'open_ctree failed', " Ken D'Ambrosio
2011-01-07 20:31 ` cwillu
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=AANLkTint9312XUw3LqHWTyP5_LQTaUgRzXE8KfBdbYta@mail.gmail.com \
--to=cwillu@cwillu.com \
--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).