On Fri, Apr 26, 2019 at 12:27 PM Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote: > > btrfs send/receive expects subvolumes to remain read-only. As soon as > you start fiddling with read-only status you already lost. btrfs should > have never allowed to change read-only into read-write in the first place. I'm in agreement, and would like to see 'btrfs property set <> ro false> removed. It's confusing. Once a subvolume is read-only, it should remain read-only, and if the use case requires rw, then just snapshot it (default rw). -- Chris Murphy
