linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>, fdmanana@gmail.com
Subject: How to change/fix 'Received UUID'
Date: Mon, 5 Mar 2018 08:16:19 -0800	[thread overview]
Message-ID: <20180305161619.prnkl4q4zcyibzhc@merlins.org> (raw)

Howdy,

I did a bunch of copies and moving around subvolumes between disks and
at some point, I did a snapshot dir1/Win_ro.20180205_21:18:31 dir2/Win_ro.20180205_21:18:31

As a result, I lost the ro flag, and apparently 'Received UUID' which is
now preventing me from restarting the btrfs send/receive.

I changed the snapshot back to 'ro' but that's not enough:

Source:
        Name:                   Win_ro.20180205_21:18:31
        UUID:                   23ccf2bd-f494-e348-b34e-1f28486b2540
        Parent UUID:            -
        Received UUID:          3cc327e1-358f-284e-92e2-4e4fde92b16f
        Creation time:          2018-02-15 20:14:42 -0800
        Subvolume ID:           964
        Generation:             4062
        Gen at creation:        459
        Parent ID:              5
        Top level ID:           5
        Flags:                  readonly

Dest:
        Name:                   Win_ro.20180205_21:18:31
        UUID:                   a1e8777c-c52b-af4e-9ce2-45ca4d4d2df8
        Parent UUID:            -
        Received UUID:          -
        Creation time:          2018-02-17 22:20:25 -0800
        Subvolume ID:           94826
        Generation:             250714
        Gen at creation:        250540
        Parent ID:              89160
        Top level ID:           89160
        Flags:                  readonly

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
2) force a btrfs receive to work despite the lack of matching 'Received
UUID' 

Yes, I could discard and start over, but my 2nd such subvolume is 8TB,
so I'd really rather not :)

Any ideas?

Thanks,
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/                       | PGP 7F55D5F27AAF9D08

             reply	other threads:[~2018-03-05 16:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 16:16 Marc MERLIN [this message]
2018-03-05 19:38 ` How to change/fix 'Received UUID' 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
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=20180305161619.prnkl4q4zcyibzhc@merlins.org \
    --to=marc@merlins.org \
    --cc=fdmanana@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).