On Mon, Jan 21, 2019 at 3:23 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > I literally never use the 'property set' feature to set ro and unset > ro because I think it's dangerous. Also, there is a distinction between 'btrfs snapshot -r' and 'btrfs property set ro true' - the former creates a snapshot. The later creates a read only subvolume. They aren't the same thing. If you try both methods and then point 'btrfs sub show' to each original subvolume, you will see only the snapshot is tracked as a snapshot, and only a snaphot properly has its own unique UUID as well as a referencing parent UUID. That is why your workflow is failing. Not that 'property set' is somehow broken; I consider it dangerous to combine a snapshotting workflow with one that depends on unsetting the ro flag on a snapshot, where you make changes to that snapshot outside the snapshotting regimen. Doing so makes that subvolume/snapshot totally invalid as either a parent or source for send/receive. -- Chris Murphy
