Stefan, the second issue you're seeing was discussed here: http://www.spinics.net/lists/linux-btrfs/msg19672.html You can apply the patch I sent there meanwhile, but as Miao pointed out, I will need to make a better patch (hope will do it soon, together with this one). Thanks, Alex. On Mon, Oct 15, 2012 at 10:06 PM, Stefan Priebe <s.priebe@xxxxxxxxxxxx> wrote: > Am 15.10.2012 21:42, schrieb Alex Lyakas: > >> Is /btrfs/target/\@snapshot/ a subvolume or a directory? > > A simple directory. > > >> can you pls try the patch that I posted here: >> http://www.spinics.net/lists/linux-btrfs/msg19583.html >> >> I feel that you're hitting a similar issue here. Before you apply the >> patch, please verify that you have /etc/mtab on your system (I will >> make a more formal patch later). > > > With your patch it works FINE!! Great! > > Another problem i'm seeing is: > > # btrfs send -i /btrfs/src/\@snapshot/1 /btrfs/src/\@snapshot/2 | btrfs > receive /btrfs/target/\@snapshot/ > At subvol /btrfs/src/@snapshot/2 > ERROR: Failed to lookup path for root 0 - No such file or directory > ERROR: unable to resolve path for root 350 > > Then i have to wait some seconds and the same command works fine. I see the > same with btrfs subvolume list PATH > > and it is unrelated to your patch. > > Stefan -- 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
