Em 02-07-2013 13:05, Stefan Behrens escreveu:
The reason why you are not able to send an incremental snapshot back
(as you tried it in your previous mail) is that the implementation
cannot handle it. The receive side gets a parent_uuid (in case of
incremental transfers using the "-p" option), this parent_uuid is
matched to the fields received_uuid of the subvolumes in the receive
filesystem. If no match is found, the receive fails. And that is what
happens.
If you look at the following script, you can see the expected
parent_uuid in the line before the "ERROR: could not find parent
subvolume". And when you look at the output of "btrfs subv list ...
/mnt/a", you notice that no subvolume at all has the field ruuid
(which stands for received_uuid) set to any valid value. Therefore it
doesn't match, therefore it fails.
This logic could be changed, but that's how it is today.
Hi Stefan,
Thank you for the detailed explanation, I guess I understand it better
now. I guess for the time being I have to use rsync to get the data back
or transfer the whole subvolume back.
thanks,
--
Miguel Negrão
http://www.friendlyvirus.org/miguelnegrao
--
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
