http://bugzilla.suse.com/show_bug.cgi?id=1025051 Bug ID: 1025051 Summary: Btrfs: use received_uuid of parent during send Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm@suse.com Reporter: jeffm@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- From: Josef Bacik Date: Thu, 4 Jun 2015 17:17:25 -0400 Subject: Btrfs: use received_uuid of parent during send Git-commit: 37b8d27de5d0079e1ecef2711061048e13054ebe Patch-mainline: v4.2-rc2 References: revisit Neil Horman pointed out a problem where if he did something like this receive A snap A B change B send -p A B and then on another box do recieve A receive B the receive B would fail because we use the UUID of A for the clone sources for B. This makes sense most of the time because normally you are sending from the original sources, not a received source. However when you use a recieved subvol its UUID is going to be something completely different, so if you then try to receive the diff on a different volume it won't find the UUID because the new A will be something else. The only constant is the received uuid. So instead check to see if we have received_uuid set on the root, and if so use that as the clone source, as btrfs receive looks for matches either in received_uuid or uuid. Thanks, Reported-by: Neil Horman Signed-off-by: Josef Bacik Reviewed-by: Hugo Mills Signed-off-by: Chris Mason Acked-by: Jeff Mahoney --- fs/btrfs/send.c | 25 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.