From: Chris Murphy <lists@colorremedies.com>
To: Alberto Bursi <alberto.bursi@outlook.it>
Cc: "Swâmi Petaramesh" <swami@petaramesh.org>,
"Chris Murphy" <lists@colorremedies.com>,
"Piotr Szymaniak" <szarpaj@grubelek.pl>,
"Andrei Borzenkov" <arvidjaar@gmail.com>,
"Linux BTRFS Mailinglist" <linux-btrfs@vger.kernel.org>
Subject: Re: Cloning / getting a full backup of a BTRFS filesystem
Date: Wed, 4 Sep 2019 20:47:27 -0600 [thread overview]
Message-ID: <CAJCQCtTJ36JR7xbr1kO5hARn3Tsm3Far8JWzLo+xMUNXhptswQ@mail.gmail.com> (raw)
In-Reply-To: <DB7P191MB0377435B086CBC80B5713B1192B80@DB7P191MB0377.EURP191.PROD.OUTLOOK.COM>
On Wed, Sep 4, 2019 at 4:14 PM Alberto Bursi <alberto.bursi@outlook.it> wrote:
>
> There is a python-based tool that can clone a btrfs volume by sending
> subvolumes to the new filesystem,
> one at a time. I never tried it, but it has a bunch of options, a decent
> readme and it's still maintained so
> you may ask its developer too about your case.
>
> https://github.com/mwilck/btrfs-clone
Wow this is really cool! Just reading the readme is enlightening.
--
Chris Murphy
next prev parent reply other threads:[~2019-09-05 2:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 6:15 Cloning / getting a full backup of a BTRFS filesystem Swâmi Petaramesh
2019-09-04 9:03 ` Andrei Borzenkov
2019-09-04 14:04 ` Piotr Szymaniak
2019-09-04 20:20 ` Hugo Mills
2019-09-04 20:48 ` Chris Murphy
2019-09-04 21:04 ` Swâmi Petaramesh
2019-09-04 22:01 ` Chris Murphy
2019-09-04 22:14 ` Alberto Bursi
2019-09-05 2:47 ` Chris Murphy [this message]
2019-09-05 4:59 ` Swâmi Petaramesh
2019-09-04 17:55 ` Chris Murphy
2019-09-04 20:51 ` Chris Murphy
2019-09-05 13:06 ` Anand Jain
2019-09-05 13:13 ` Qu Wenruo
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=CAJCQCtTJ36JR7xbr1kO5hARn3Tsm3Far8JWzLo+xMUNXhptswQ@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=alberto.bursi@outlook.it \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.org \
--cc=szarpaj@grubelek.pl \
/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.