From: Marc MERLIN <marc@merlins.org>
To: Terrance Harris <tharrisone@polarismail.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Fun BTRFS Stuff:
Date: Mon, 22 Feb 2016 13:11:42 -0800 [thread overview]
Message-ID: <20160222211142.GD4913@merlins.org> (raw)
In-Reply-To: <56CB737D.1020403@polarismail.net>
On Mon, Feb 22, 2016 at 02:45:49PM -0600, Terrance Harris wrote:
> Hello,
>
> I'm a btrfs novice, but i've been using it for a few years now on
> openSUSE Tumblweed.
Howdy.
First, please use the linux-btrfs@vger.kernel.org mailing list
> Is there a way to convert snaBpshots into mountable files using btrfs send?
I am not sure I'm parsing your question.
btrfs send/receive copy read only snapshots between 2 btrfs volumes
If you mean using a non differential btrfs send to a file, and then using
that file to act as if it were a filesystem you can read data from, I don't
believe this is easily possible currently (it's possible, just no tool
exists to do that). You're supposed to send it to btrfs receive, have it
saved on a filesystem, and then use that.
> I'm looking make it easy to copy off btrfs files even if my btrfs system
> is in total fubar mode.
you need to send that btrfs send stream to btrfs receive onto another
filesystem, and use that for restores.
Hope this helps
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next parent reply other threads:[~2016-02-22 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56CB737D.1020403@polarismail.net>
2016-02-22 21:11 ` Marc MERLIN [this message]
2016-02-22 21:18 ` Fun BTRFS Stuff: Hugo Mills
2016-02-23 0:19 ` Duncan
2016-02-25 2:07 ` Henk Slager
2016-02-25 4:18 ` Duncan
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=20160222211142.GD4913@merlins.org \
--to=marc@merlins.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=tharrisone@polarismail.net \
/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.