Hi

This process used to work. I am not sure what is going wrong now and/or what requirements have changed. I'd really appriecate another set of eyes looking at this.

The sending volume has:
# btrfs subvol list -pqu /snap ID 258 gen 416417 parent 5 top level 5 parent_uuid - uuid 6447cef2-9b1a-c146-8dc3-b759ed2dd694 path homevol ID 749 gen 399865 parent 258 top level 258 parent_uuid 6447cef2-9b1a-c146-8dc3-b759ed2dd694 uuid c309c50a-8558-a242-86bd-d64b7f6ca0cd path homevol/backup ID 750 gen 401012 parent 258 top level 258 parent_uuid 6447cef2-9b1a-c146-8dc3-b759ed2dd694 uuid d29ffd19-8ca1-e248-ace0-fc174902f1f3 path homevol/backup.2015-27-6_07-04_22:00

The recieving volume has:
# btrfs subvol list -pquR /backup | grep c309c50a-8558-a242-86bd-d64b7f6ca0cd ID 3698 gen 3116 parent 5 top level 5 parent_uuid - received_uuid c309c50a-8558-a242-86bd-d64b7f6ca0cd uuid 18a46efa-3cc3-4742-925e-ea0681709592 path home/backup

But send/recieve is not working:
# btrfs send -ve -p homevol/backup homevol/backup.2015-27-6_07-04_22:00 | btrfs receive -v /backup/home
At subvol homevol/backup.2015-27-6_07-04_22:00
At snapshot backup.2015-27-6_07-04_22:00
receiving snapshot backup.2015-27-6_07-04_22:00 uuid=d29ffd19-8ca1-e248-ace0-fc174902f1f3, ctransid=401012 parent_uuid=cb3ad856-ca0f-f744-b7c3-b33f2d5bc8d3, parent_ctransid=399865
ERROR: could not find parent subvolume

Yet the subvol homevol/backup has been sent (full) to and exists on /backup filesystem as can be seen in the two subvol lists, yet send/recieve cannot seem to find it for an incremental backup.
Why?

TIA
Ed Tomlinson
--
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

Reply via email to