On Sun, May 10, 2015 at 9:55 PM, Duncan <1i5t5.duncan@xxxxxxx> wrote: > Marc MERLIN posted on Sun, 10 May 2015 09:49:44 -0700 as excerpted: > >> Are there any plans for a full filesystem send/receive, not just a >> subvolume send/receive? > > Recent discussion suggests yes, tho it's a relatively new plan. > > More specifically, the recent discussion seemed to settle around the need > for a send/receive --recursive option, which would recurse into nested > subvolumes. IIRC, the systemd folks requested that for their container > management, among other things. That was for snapshot creation and destruction, not send receive. To me, an exact Btrfs clone suggests only a Btrfs destination at the moment, because there's no superset functionality elsewhere for everything in Btrfs to exist. One way to get to an "exact clone" would be Btrfs seed device to effectively freeze the original, and then "send" the entire seed somehow rather than just a subvolume. A btrfs send file on non-Btrfs destinations, is a maybe, the problem there is no checksums exist in the send file and maybe some other things (?) but presumably that could be extended so that the file could be a complete representation of the file system warts and all - which itself may not be desirable so it's like, how exactly do we really want these things to be? Hmm? -- Chris Murphy -- 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
