On Fri, 2014-01-03 at 12:15 -0800, Marc MERLIN wrote: +AD4- On Mon, Dec 30, 2013 at 09:57:40AM -0800, Marc MERLIN wrote: +AD4- +AD4- On Mon, Dec 30, 2013 at 10:48:10AM -0700, Chris Murphy wrote: +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- On Dec 30, 2013, at 10:10 AM, Marc MERLIN +ADw-marc+AEA-merlins.org+AD4- wrote: +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- If one day, it could at least work on a subvolume level (only sync a +AD4- +AD4- +AD4- +AD4- subvolume), then it would be more useful to me. Maybe later+ICY- +AD4- +AD4- +AD4- +AD4- +AD4- +AD4- Maybe I'm missing something, but btrfs send/receive only work on a subvolume level. +AD4- +AD4- +AD4- +AD4- Never mind, I seem to be the one being dense. I mis-read that you needed +AD4- +AD4- to create the filesystem with btrfs receive. +AD4- +AD4- Indeed, it's on a subvolume level, so it's actually fine since it does +AD4- +AD4- allow over provisionning afterall. +AD4- +AD4- Mmmh, but I just realized that on my laptop, I do boot the btrfs copy +AD4- (currently done with rsync) from time to time (i.e. emergency boot from +AD4- the HD the SSD was copied to). +AD4- If I do that, it'll change the filesystem that was created with btrfs +AD4- receive and break it, preventing further updates, correct? +AD4- +AD4- If so, can I get around that by making a boot snapshot after each copy +AD4- and mount that snapshot for emergency boot instead of the main volume? Yes that will work. -chris -- 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
