Sometimes when using btrfs send-receive, I get errors like this: ERROR: parent determination failed for <subvolume name>
When this happens, btrfs send-receive backups fail. And all subsequent backups fail too. The issue seems to stem from the fact that an automated cleanup process removes certain earlier subvolumes. (I'm using Snapper.) I'd like to understand exactly what is happening so that my backups do not unexpectedly fail. In my scenario, no parent subvolumes have been deleted from the target. Some subvolumes have been deleted from the source, but why does that matter? I am able to take a valid snapshot at this time and every snapshot ever taken continues to reside at the target backup destination (seemingly meaning that a parent subvolume can be found at the target). This issue seems to make btrfs send-receive a very fragile backup solution. I hope, instead, there is some knowledge I'm missing, that when learned, will make this a robust backup solution. Thanks -- 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
