On Tue, Sep 19, 2017 at 3:37 PM, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote: > 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? No. I never mount the 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. Well, that's not exactly my issue but it still helps me gain additional understanding. It may help me reproduce my original problem too. Thank you. > > > 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. Thank you for this also. I will simply edit my current copy of the snap-sync script to use "-p" now. That's a simple change I am implement immediately. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
