On 2019-07-17 3:45 a.m., Bernhard Kühnel wrote: > > I believe the usual practice is to create snapshots with the -r flag and > follow some naming convention (e.g. place them in a common .snapshots > folder named by date), but you're free to switch between read-only and > read-write mode for a snapshot at any time using the btrfs property command. > > That allows for some intereresting feats: e.g. there's no guarantee that > a (now) read-only snapshot actually reflects the source's state at > creation time (if someone modified it and re-applied the ro flag). On > the other hand, reverting to a snapshotted state may be as easy as > making the snapshot rw and changing the mount options to use it's > subvolid - no need to copy any files back and forth. >
You should *really* not do this. Switching subvolumes between rw and ro will break assumptions that send/receive rely on in interestingly disastrous, sometimes silent ways. The proper way to make a ro subvolume snapshot rw is to create a new snapshot of it.
signature.asc
Description: OpenPGP digital signature
