Thank you very much for your response.
I had just discovered exactly this a few hours ago. In sending an
original snapshot instead of using a duplicate already in place, I was
able to get around this problem.
As you mentioned, the error was coming from the receive side.
I am presently investigating a another error I have detailed in another
message:
ERROR: rename o3528-7220-0 -> usr failed: Directory not empty
It is probably not related. I will file a report with Kernel.org
bugzilla on it.
On 04/30/2017 04:43 PM, Chris Murphy wrote:
On Sat, Apr 29, 2017 at 9:10 PM, J. Hart <jfhart...@gmail.com> wrote:
I am trying to do a "send -p src/snp1 src/snp2 dst/" and getting the
following error:
ERROR: cannot find parent subvolume
The "src/snp1" is present in both "src/" and "dst/".
It's not merely that it must be present. The src/snp1 must have
originally been sent to dst/ using btrfs send/receive. And in
particular it's trying to match subvolume UUIDs; so really the error
is "cannot find parent subvolume uuid on the destination" - at least
I *think* that's what's going on.
You'd need to use -v or possibly -vv with both the send and receive
commands to get more verbose output and maybe see whether it's the
send or receive side having the problem. I'm gonna guess it's the
receive side.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
