From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: how to clone a btrfs filesystem
Date: Sat, 18 Apr 2015 19:23:16 +0200 [thread overview]
Message-ID: <1429377796.9230.4.camel@scientia.net> (raw)
In-Reply-To: <CAJCQCtQVjrkfPykDv5H0uC08nPq3KLu+PmV_2suoaambV1Sumw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
On Sat, 2015-04-18 at 10:20 -0600, Chris Murphy wrote:
> Make the source a seed device, add new device, delete seed. Once that
> completes, unmount, unset btrfs seed, and now the two devices are
> separate fs volumes each with unique UUID. There may still be bugs
> with seed device, it's been maybe 6 months since I last checked.
Hmm but that also modifies the source fs, at least the seed device part,
right?
Given that all this apparently contains still bugs, I'd have rather kept
the source fs read only.
Also, AFAIU this would work only once then.... and I wouldn't be able to
do incremental backups, would I?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
prev parent reply other threads:[~2015-04-18 17:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 23:08 how to clone a btrfs filesystem Christoph Anton Mitterer
2015-04-18 4:24 ` 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 [this message]
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=1429377796.9230.4.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).