From: Marc MERLIN <marc@merlins.org>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
fdmanana@gmail.com
Subject: Re: How to change/fix 'Received UUID'
Date: Thu, 8 Mar 2018 11:26:50 -0800 [thread overview]
Message-ID: <20180308192650.GA2930@merlins.org> (raw)
In-Reply-To: <fe4cd21d-aed1-2509-1c8a-fb4f1e805ce0@gmail.com>
On Thu, Mar 08, 2018 at 09:36:49PM +0300, Andrei Borzenkov wrote:
> Yes. Your source has Received UUID. In this case btrfs send will
> transmit received UUID instead of subvolume UUID as reference to base
> snapshot. You need to either clear received UUID on source or set
> received UUID on destination to received UUID of source (not to
> subvolume UUID of source).
gargamel:/var/local/src/python-btrfs/examples# ./set_received_uuid.py 0e220a4f-6426-4745-8399-0da0084f8b23 313
37 1234.5678 /mnt/btrfs_bigbackup/DS1/Video_ro.20180220_21:03:41
Current subvolume information:
subvol_id: 94887
received_uuid: 2afc7a5e-107f-d54b-8929-197b80b70828
stime: 1234.5678 (1970-01-01T00:20:34.567800)
stransid: 31337
rtime: 1520488877.415709329 (2018-03-08T06:01:17.415709)
rtransid: 255755
Setting received subvolume...
Resulting subvolume information:
subvol_id: 94887
received_uuid: 0e220a4f-6426-4745-8399-0da0084f8b23
stime: 1234.5678 (1970-01-01T00:20:34.567800)
stransid: 31337
rtime: 1520537034.890253770 (2018-03-08T19:23:54.890254)
rtransid: 256119
gargamel:/var/local/src/python-btrfs/examples# btrfs property set -ts /mnt/btrfs_bigbackup/DS1/Video_ro.201802
20_21:03:41 ro true
This worked fine, thank you so much.
I now have an incremental send that is going on and will take a few dozen minutes instead
of days for 8TB+ :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2018-03-08 19:26 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
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 [this message]
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=20180308192650.GA2930@merlins.org \
--to=marc@merlins.org \
--cc=arvidjaar@gmail.com \
--cc=dsterba@suse.com \
--cc=fdmanana@gmail.com \
--cc=hans.van.kranenburg@mendix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.