From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send receive, clone
Date: Thu, 24 Apr 2014 17:29:29 +0100 [thread overview]
Message-ID: <20140424162929.GH2391@carfax.org.uk> (raw)
In-Reply-To: <20140424155510.GG2391@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
On Thu, Apr 24, 2014 at 04:55:10PM +0100, Hugo Mills wrote:
> I'm trying to think of a case where -c is useful that doesn't
> involve someone having done cp --reflink=always between subvolumes,
> but I can't.
OK, you can use -c if you don't have a record of the relationships
between the subvolumes you want to send, but know that they're related
in some way. As above, you send the first subvol "bare", and then
supply a -c for each one that you've already sent.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- echo "killall cat" > ~/curiosity.sh ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-04-24 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 15:23 btrfs send receive, clone Chris Murphy
2014-04-24 15:55 ` Hugo Mills
2014-04-24 16:29 ` Hugo Mills [this message]
2014-04-24 17:22 ` Chris Murphy
2014-04-24 18:45 ` Hugo Mills
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=20140424162929.GH2391@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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