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 invest
On Sat, Apr 29, 2017 at 9:10 PM, J. Hart 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 hav
Thank you very much for your thoughtful and thorough reply. I
appreciate this very much.
I have finally been able to work past the issue. It seems that
send/receive participates in maintaing some sort of "chain of
custody/ancestry". I had been using a pre-existing snapshot at the
destinat
J. Hart posted on Sat, 29 Apr 2017 23:10:48 -0400 as excerpted:
> 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/". The "src/snp2" is
> present in "src/" .
> T
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/". The "src/snp2" is
present in "src/" .
The send works when "-p" is not used, but will not work when it is.
I imagine