Your message dated Fri, 27 Dec 2024 15:45:20 -0700
with message-id <[email protected]>
and subject line Re: Bug#1019377: ERROR: cannot flip ro->rw with received_uuid
set
has caused the Debian Bug report #1019377,
regarding ERROR: cannot flip ro->rw with received_uuid set
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1019377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019377
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 property set -ts /btrfs/test/mysubvol ro false
ERROR: cannot flip ro->rw with received_uuid set, use force if you really want
that
The subvolume is sent/received using the following command:
sudo btrfs send mysubvol | ssh user@host sudo btrfs receive /btrfs/test/
Adding the -f flag as suggested by the error message helps but it's not
clear what the implication of this are. I tried to search the internet
for this error but only found instances of others running into it with
no insight into what it means.
--- End Message ---
--- Begin Message ---
Control: tag -1 moreinfo upstream wontfix
Nicholas D Steeves <[email protected]> writes:
> Boris Kolpackov <[email protected]> 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 of the received subvol, use
> it for whatever purposes you need to write to it for, and then delete
> the temporary rw snapshot subvol? This approach doesn't compromise the
> integrity of your replica.
>
>> 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?
>
> What problem are you attempting to solve?
As it has been almost a year without an update, I am closing this bug as
"moreinfo, upstream, wontfix". Please reply if closing this bug seems
in error and/or unfair.
Regards,
Nicholas
signature.asc
Description: PGP signature
--- End Message ---
