Adam Borowski <kilob...@angband.pl> writes: > If you modify the subvolume, you can't use it for incremental send/receive > anymore. > > The commit that introduced this says: > > Implement safety check when a read-only subvolume is getting switched > to read-write and there's received_uuid set. > > This prevents accidental breakage of incremental send use case but > allows user to do the rw change anyway but resets the received_uuid in > that case.
Thanks for the clarification. Interestingly, in my use case I do want to be able to do incremental send/receive and the only reason I am temporarily clearing the read-only property is to change the subvolume's owner: sudo btrfs property set -f -ts ./subvol ro false sudo chown user:user ./subvol sudo chown user:user ./subvol/* btrfs property set -ts ./subvol ro true I wonder if there is now a way to achieve this without clearing received_uuid?
