From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Axel Burri <axel@tty0.ch>, Dave <davestechshop@gmail.com>,
linux-btrfs@vger.kernel.org
Cc: A L <crimsoncottage@gmail.com>
Subject: Re: send | receive: received snapshot is missing recent files
Date: Tue, 12 Sep 2017 06:19:48 +0300 [thread overview]
Message-ID: <f7adba0b-9464-0d75-28f3-3b90187ee14e@gmail.com> (raw)
In-Reply-To: <0f1e32f8-12c7-4aa7-246f-4f6805e6d3df@tty0.ch>
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.
next prev parent reply other threads:[~2017-09-12 3:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 5:37 send | receive: received snapshot is missing recent files Dave
[not found] ` <CAH=dxU7RM7s+pxT=wxE9WcUNMWjSG_A0=1pUWD1dWGVQ6g+g8Q@mail.gmail.com>
2017-09-06 19:46 ` Dave
2017-09-07 4:43 ` Dave
2017-09-07 6:24 ` A L
2017-09-07 12:39 ` Dave
2017-09-07 13:34 ` Dave
2017-09-07 14:33 ` Axel Burri
2017-09-08 4:44 ` Dave
2017-09-11 17:53 ` Axel Burri
2017-09-12 3:19 ` Andrei Borzenkov [this message]
2017-09-13 16:52 ` Dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7adba0b-9464-0d75-28f3-3b90187ee14e@gmail.com \
--to=arvidjaar@gmail.com \
--cc=axel@tty0.ch \
--cc=crimsoncottage@gmail.com \
--cc=davestechshop@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).