On Sat, Jan 23, 2016 at 4:55 PM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: > On Sat, Jan 23, 2016 at 04:48:26PM -0700, Chris Murphy wrote: >> https://bugzilla.kernel.org/show_bug.cgi?id=111221 >> >> 4.4.0-1.fc24.x86_64 >> btrfs-progs-4.3.1-1.fc23.x86_64 >> >> >> >> [...snip...] >> BTRFS_IOC_SEND returned 0 >> joining genl thread >> At subvol testsub.1 >> ERROR: parent determination failed for 0 > > This looks to me like a known and somewhat awkward bug/misfeature > where the mountpoint containing either the subvol being sent or the > target location for the receive is not a top-level mount, which causes > this error. i.e., this will (I think) fail: > > # mount -o subvol=@foo /dev/sda1 /mnt > # btrfs send /mnt/@whatever | ... > > Can you try again from within a subvolid=0 mount? No change in behavior. /dev/mapper/luks on /brick1 type btrfs (rw,relatime,seclabel,space_cache,subvolid=5,subvol=/) /dev/sda1 on /mnt type btrfs (rw,relatime,seclabel,space_cache,subvolid=5,subvol=/) [root@f23s ~]# btrfs send -e /mnt/root23s/root/testsub.* | btrfs receive /brick1/ At subvol /mnt/root23s/root/testsub.0 At subvol testsub.0 At subvol /mnt/root23s/root/testsub.1 ERROR: parent determination failed for 0 ERROR: unexpected EOF in stream. [root@f23s ~]# btrfs send -e /mnt/root23s/root/testsub.0 /mnt/root23s/root/testsub.1 /mnt/root23s/root/testsub.2 /mnt/root23s/root/testsub.3 /mnt/root23s/root/testsub.4 | btrfs receive /brick1/ At subvol /mnt/root23s/root/testsub.0 At subvol testsub.0 At subvol /mnt/root23s/root/testsub.1 ERROR: parent determination failed for 0 ERROR: unexpected EOF in stream. Chris Murphy -- Chris Murphy -- 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
