On Wed, Feb 22, 2017 at 11:56:37PM +0100, Benedikt Morbach wrote: > testcase: > # ro subvol /src/parent > # rw subvol /src/foo > clone /src/parent/file /src/foo/file > subvol snapshot -r /src/foo /src/foo.snap > > # generates a "clone parent/file -> foo.snap/file" send command > send -p /src/parent /src/foo.snap > > # target fs: > # dest/ > # |--- parent/... > # mounted with -o subvol=dest, such that "parent" is at <target>/parent > receive <target> > > result: > ERROR: cannot open dest/parent/file: No such file or directory > > expected: > "dest/" get's stripped from the clone source path to get the actual > path in the target fs, if reachable from the mount point/chroot. > > This is exactly what process_snapshot does, which gets called on > _every_ incremental receive and I'm quite certain is correct in > doing so > > Signed-off-by: Benedikt Morbach <[email protected]>
1-2 applied, thanks. > --- > > Hi, > > I first tried fixing this ages ago with [1], which was met with some > scepticism. > While that patch wasn't 100% correct I believe this is, and as mentioned it > does > exacly the same thing as process_snapshot because that has the exact same > problem. > > An fstest to reproduce this will be following shortly I'll add an adapted version of the test script to progs as I'd like to be able to test any changes to receive from there. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
