11.09.2017 20:53, Axel Burri пишет: > On 2017-09-08 06:44, Dave wrote: >> I'm referring to the link below. Using "btrfs subvolume snapshot -r" >> copies the Received UUID from the source into the new snapshot. The >> btrbk FAQ entry suggests otherwise. Has something changed? > > I don't think something has changed, the description for the read-only > subvolumes on the btrbk FAQ was just wrong (fixed now). > >> The only way I see to remove a Received UUID is to create a rw >> snapshot (above command without the "-r"), which is not ideal in this >> situation when cleaning up readonly source snapshots. >> >> Any suggestions? Thanks > > No suggestions from my part, as far as I know there is no way to easily > remove/change a received_uuid from a subvolume. >
There is BTRFS_IOC_SET_RECEIVED_SUBVOL IOCTL which is used by "btrfs received". My understanding is that it can also be set to empty (this clearing it). You could write small program to do it. In general it sounds like a bug - removing read-only flag from subvolume by any means should also clear Received UUID as we cannot anymore guarantee that subvolume content is the same. -- 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
