Boris Kolpackov writes:
> 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:
Why don't you create of a normal rw snapshot
Adam Borowski 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
On Thu, Sep 08, 2022 at 09:04:23AM +0200, Boris Kolpackov wrote:
> After upgrading from btrfs-progs 5.14.1-1 with Linux kernel 5.14.9 to
> btrfs-progs 5.18.1-1 with Linux kernel 5.18.16 (from current testing)
> I see the following new error when trying to clear the read-only
> property of a
Package: btrfs-progs
Version: 5.18.1-1
After upgrading from btrfs-progs 5.14.1-1 with Linux kernel 5.14.9 to
btrfs-progs 5.18.1-1 with Linux kernel 5.18.16 (from current testing)
I see the following new error when trying to clear the read-only
property of a freshly received snapshot:
btrfs
4 matches
Mail list logo
