Hi, > Subvol A on source side: (A, -) > Send this to A' on target side: (A', A) > Send this back to A'' on source side: (A'', A) <-- Note the A here, not A'
I also think your approach is the real solution to the problem, but as some pointed out on IRC this changes the behaviour of btrfs receive and will break things for someone. When I asked whose obscure workflow does it break nobody could come up with any reasonable example whereas sending snapshots back and forth seems to be the major usecase for btrfs receive and it's impossible to for example restore snapshots with current implementation. I know that -p may fail horribly but the idea was to have *option* to replace parent lookup logic and instead of relying on UUID-s simply have it specified by userspace application. > More later, when I've had a little time to play with things and > think through the semantics properly. You want to give it a try? -- Lauri Võsandi tel: +372 53329412 e-mail: lauri.vosa...@gmail.com blog: http://lauri.vosandi.com/ -- 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
