18.09.2017 11:45, Graham Cobb пишет: > On 18/09/17 07:10, Dave wrote: >> For my understanding, what are the restrictions on deleting snapshots? >> >> What scenarios can lead to "ERROR: parent determination failed"? > > The man page for btrfs-send is reasonably clear on the requirements > btrfs imposes. If you want to use incremental sends (i.e. the -c or -p > options) then the specified snapshots must exist on both the source and > destination. If you don't have a suitable existing snapshot then don't > use -c or -p and just do a full send. >
Well, I do not immediately see why -c must imply incremental send. We want to reduce amount of data that is transferred, so reuse data from existing snapshots, but it is really orthogonal to whether we send full subvolume or just changes since another snapshot. >> I use snap-sync to create and send snapshots. >> >> GitHub - wesbarnett/snap-sync: Use snapper snapshots to backup to external >> drive >> https://github.com/wesbarnett/snap-sync > > I am not familiar with this tool. Your question should be sent to the > author of the tool, if that is what is deciding what -p and -c options > are being used. > I am not sure how it could come to this error. I looked on more or less default installation of openSUSE here and all snapper snapshots have as parent UUID the subvolume that is mounted as root (by default only one configuration for root subvolume exists). So it is not possible to remove this subvolume, unless some rollback to another snapshot was performed. -- 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
