[<<][pool][>>][..]
Wed Nov 30 16:34:01 EST 2016

sending subvolumes

Apparently you can't "chain sends" with btrfs.

E.g. sending

snapshot_1,host_A -> snapshot_1,host_B


on host_B:  snapshot_1 -> snapshot (rw, then modify) -> snapshot_2

snapshot_2,host_B -> parent of snapshot_2,host_B

now snapshot_1,host_A is no longer the parent of snapshot_1,host_A


is it possible to re-parent snapshot_2 to snapshot_1?


http://linux-btrfs.vger.kernel.narkive.com/MmG4jI9S/incremental-btrfs-receive-in-opposite-direction-fails
http://unix.stackexchange.com/questions/251114/copy-remote-btrfs-incremental-snapshot-to-new-drive-w-uuid
https://www.spinics.net/lists/linux-btrfs/msg44486.html
https://www.spinics.net/lists/linux-btrfs/msg44089.html


Maybe this is really not intended to work like that..
It seems rather complicated.

Let's just use this for keeping track of backups for now, and put the
"core" filesystem on a dedicated disk, keep that as the germ line, and
possibly fork off temporary working copies.  It would also make it
clear how to use it: external drive = master, and perform updates only
on master.



[Reply][About]
[<<][pool][>>][..]