linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: how to clone a btrfs filesystem
Date: Sat, 18 Apr 2015 01:08:44 +0200	[thread overview]
Message-ID: <1429312124.8371.62.camel@scientia.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

Hey.

I've seen that this has been asked some times before, and there are
stackoverflow/etc. questions on that, but none with a really good
answer.

How can I best copy one btrfs filesystem (with snapshots and subvolumes)
into another, especially with keeping the CoW/reflink status of all
files?
And ideally incrementally upgrade it later (again with all
snapshots/subvols, and again not loosing the shared blocks between these
files).

send/receive apparently also works for just one subvolume,... and
documentation is quite sparse :-/


Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]

             reply	other threads:[~2015-04-17 23:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 23:08 Christoph Anton Mitterer [this message]
2015-04-18  4:24 ` how to clone a btrfs filesystem Russell Coker
2015-04-18  5:17   ` Christoph Anton Mitterer
2015-04-18 15:02     ` Russell Coker
2015-04-19  3:56       ` Duncan
2015-04-19 20:00       ` Christoph Anton Mitterer
2015-04-20  5:23         ` Duncan
2015-04-20 16:32           ` Christoph Anton Mitterer
2015-04-18  8:10 ` Martin Steigerwald
2015-05-07  5:14   ` Paul Harvey
2015-05-07 18:57     ` Martin Steigerwald
2015-05-08  3:22       ` Paul Harvey
2015-04-18 16:09 ` Kai Krakow
2015-04-18 16:23   ` Kai Krakow
2015-04-18 16:23   ` Chris Murphy
2015-04-18 16:36     ` Kai Krakow
2015-04-19 20:33       ` Chris Murphy
2015-04-18 16:20 ` Chris Murphy
2015-04-18 17:23   ` Christoph Anton Mitterer

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=1429312124.8371.62.camel@scientia.net \
    --to=calestyo@scientia.net \
    --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).