On Mon, May 05, 2014 at 03:24:45AM +0000, Duncan wrote: > *However*: snapshotting a read-only snapshot and making the new one > writable is easy enough[1]. Just keep the originals read-only so they > can be used as parents/clones, and make a second, writable snapshot of > the first, to do your writable stuff in. > > --- > [1] Snapshotting a snapshot: I'm getting a metaphorical flashing light
I already snapshot ro snapshots as rw snapshots and that works fine. It's actually rely on this in my script: http://marc.merlins.org/perso/btrfs/post_2014-03-22_Btrfs-Tips_-Doing-Fast-Incremental-Backups-With-Btrfs-Send-and-Receive.html (skip to the bottom) # We make a read-write snapshot in case you want to use it for a chroot # and some testing with a writeable filesystem or want to boot from a # last good known snapshot. btrfs subvolume snapshot "$src_newsnap" "$src_newsnaprw" $ssh btrfs subvolume snapshot "$dest_pool/$src_newsnap" "$dest_pool/$src_newsnaprw" 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
