From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Marc MERLIN <marc@merlins.org>,
Andrei Borzenkov <arvidjaar@gmail.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, fdmanana@gmail.com
Subject: Re: How to change/fix 'Received UUID'
Date: Tue, 6 Mar 2018 20:12:15 +0100 [thread overview]
Message-ID: <b323d987-9d97-f57e-b0d6-4ff405abf91c@mendix.com> (raw)
In-Reply-To: <20180305194718.GC613@merlins.org>
On 05/03/2018 20:47, Marc MERLIN wrote:
> On Mon, Mar 05, 2018 at 10:38:16PM +0300, Andrei Borzenkov wrote:
>>> If I absolutely know that the data is the same on both sides, how do I
>>> either
>>> 1) force back in a 'Received UUID' value on the destination
>>
>> I suppose the most simple is to write small program that does it using
>> BTRFS_IOC_SET_RECEIVED_SUBVOL.
>
> Understdood.
> Given that I have not worked with the code at all, what is the best
> tool in btrfs progs, to add this to?
>
> btrfstune?
> btrfs propery set?
> other?
>
> David, is this something you'd be willing to add support for?
> (to be honest, it'll be quicker for someone who knows the code to add than
> for me, but if no one has the time, I'l see if I can have a shot at it)
If you want something right now that works, so you can continue doing
your backups, python-btrfs also has the ioctl, since v9, together with
an example of using it:
https://github.com/knorrie/python-btrfs/commit/1ace623f95300ecf581b1182780fd6432a46b24d
P.S. even when coding it in C, the documentation in that commit message
might be useful. :)
fwiw,
Hans
next prev parent reply other threads:[~2018-03-06 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 16:16 How to change/fix 'Received UUID' Marc MERLIN
2018-03-05 19:38 ` Andrei Borzenkov
2018-03-05 19:47 ` Marc MERLIN
2018-03-06 19:12 ` Hans van Kranenburg [this message]
2018-03-06 20:02 ` Marc MERLIN
2018-03-08 6:06 ` Marc MERLIN
2018-03-08 6:34 ` Andrei Borzenkov
2018-03-08 16:02 ` Marc MERLIN
2018-03-08 18:36 ` Andrei Borzenkov
2018-03-08 19:26 ` Marc MERLIN
2018-03-10 18:23 ` Marc MERLIN
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=b323d987-9d97-f57e-b0d6-4ff405abf91c@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=arvidjaar@gmail.com \
--cc=dsterba@suse.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).