On Sun, May 04, 2014 at 09:54:38AM +0200, Brendan Hide wrote:
> Yes, -p (parent) and -c (clone source) are the only ways I'm aware
> of to push subvolumes across while ensuring data-sharing
> relationship remains intact. This will end up being much the same as
> doing incremental backups:
> From the man page section on -c:
> "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. It is allowed to omit the '-p <parent>'
> option when '-c <clone-src>' options are given, in which case 'btrfs
> send' will determine a suitable parent among the clone sources
> itself."
Right. I had read that, but it was not super clear to me how it can be
useful, especially if it's supposed to find the source clone by itself.
>From what you said and what I read, I think the source might be allowed
to be read write, otherwise it would be simpler for btrfs send to know
that the source has not changed.
I think I'll have to do more testing with this when I get some time.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
