18.09.2017 09:10, Dave пишет: > 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 >
Are you trying to backup top-level subvolume? I just reproduced this behavior with this tool. The problem is, snapshots of top-level subvolume do not have parent UUID (I am not even sure if UUID exists at all TBH). If you mount any other subvolume, it will work. On openSUSE root is always mounted as subvolume (actually, the very first snapshot) which explains why I did not see it before. I.e. mkfs -t btrfs /dev/sdb1 mount /dev/sdb1 /test snapper -c test create-config /test attempt to "snap-sync -c test" will fail second time. But btrfs sub create /test/@ umount /test mount -o subvol=@ /dev/sdb1 /test snapper -c test create-config /test ... will work. As I told you in the first reply, showing output of "btrfs su li -qu /path/to/src" would explain your problem much earlier. Actually if snap-sync used "btrfs send -p" instead of "btrfs send -c" it would work as well, as then no parent search would be needed (and as I mentioned in another mail both commands are functionally equivalent). But this becomes really off-topic on this list. As already suggested, open issue for snap-sync. -- 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
