All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: btrfs send receive, clone
Date: Thu, 24 Apr 2014 09:23:28 -0600	[thread overview]
Message-ID: <35B44B63-D139-4E0E-AD6F-2320B79D19B1@colorremedies.com> (raw)



I don't understand the btrfs send -c <clone-src> man page text, or really even the use case. In part this is what it says:

> You must not specify clone sources unless you
>  guarantee that these snapshots are exactly in the same state on both
>  sides, the sender and the receiver.

If the snapshots are the same on both sides, then why would I be using clone in the first place?

> -c <clone-src> Use this snapshot as a clone source for an 
> incremental send (multiple allowed)

Incremental send implies the sender and receiver are not in the same state now, but will be after the command is executed. Is one, or both, snapshots rw for -c?

Anyway, I'm lost on the specifics, but clearly I'm even lost when it comes to the basic difference between -p and -c.


Thanks,

Chris Murphy

             reply	other threads:[~2014-04-24 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 15:23 Chris Murphy [this message]
2014-04-24 15:55 ` btrfs send receive, clone Hugo Mills
2014-04-24 16:29   ` Hugo Mills
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=35B44B63-D139-4E0E-AD6F-2320B79D19B1@colorremedies.com \
    --to=lists@colorremedies.com \
    --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 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.