linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Not Zippy <notzippy@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, Not Zippy <notzippy@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs: open_ctree failed
Date: Tue, 27 Mar 2012 08:21:07 -0700	[thread overview]
Message-ID: <CANDob0Lx-kX7LHsup8m5sY=_UmyA2qXOtsxbnwtV5p+eR-2ERQ@mail.gmail.com> (raw)
In-Reply-To: <20120327130208.GC2597@carfax.org.uk>

I had found that note on the restore but my restore.c does not allow
that flag (it is also missing the "m" flag as well), I used the branch
dangerousdonteveruse on
https://git.kernel.org/?p=3Dlinux/kernel/git/mason/btrfs-progs.git I
switched to the master branch to see if there was a difference but it
does not appear to be any different. (I did find a btrfs-progs on
git-hub which appears to have those flags, but i thought the best to
use would be on git.kernel. )

Assuming I can locate the correct restore.c, is there a some other
software to determine the object id of the subvolume ?  the root
object id was 5

thanks
Nz

On Tue, Mar 27, 2012 at 6:02 AM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Tue, Mar 27, 2012 at 05:58:17AM -0700, Not Zippy wrote:
>> One entire subvolume was restored. But there were 4 subvolumes on th=
at
>> partition. Is there a way to specify/force the restore of a differen=
t
>> subvolume ?
>>
>> find-root seems to only find a single root.
>
> =A0 There is only a single root tree, so that's understandable. If yo=
u
> have a look at the documentation for restore[1], it mentions (right
> near the bottom of the page) that -r will allow you to select an
> alternative subvolume to recover from.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-03-27 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANDob0+rwkLGeJg4kP+TpPpN8VOdrOV684F5YiLC6+BkzYehHA@mail.gmail.com>
2012-03-26 21:40 ` btrfs: open_ctree failed Not Zippy
2012-03-26 21:57   ` Hugo Mills
2012-03-26 22:36     ` Not Zippy
2012-03-26 22:47       ` Hugo Mills
2012-03-27  0:20         ` Chris Samuel
2012-03-27 12:58         ` Not Zippy
2012-03-27 13:02           ` Hugo Mills
2012-03-27 15:21             ` Not Zippy [this message]
2012-03-27 17:37               ` Not Zippy
     [not found] <4EE6C49A.5070600@genome.wustl.edu>
2011-12-14 22:43 ` Samuel Just
     [not found] <CAPXeO6QbDxyoqYRhXxMGvc9JYQ6TZrTF7MwCNg-xdU-MgCQU3w@mail.gmail.com>
2011-07-07  9:20 ` Yulin, Denis

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='CANDob0Lx-kX7LHsup8m5sY=_UmyA2qXOtsxbnwtV5p+eR-2ERQ@mail.gmail.com' \
    --to=notzippy@gmail.com \
    --cc=hugo@carfax.org.uk \
    --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).