On Sat, Jan 25, 2020 at 11:18 AM Stéphane Lesimple <stephane_btrfs2@xxxxxxxxxxx> wrote: > > > ERROR: failed to clone extents to var/amavis/db/__db.001: Invalid argument > > If I may add another data point here, I'm also encountering this issue on a 5.5.0-rc6, with the btrfs-rc7 patches applied to it (so as far as btrfs is concerned, this is an rc7). > > On the first time, it happened after sending ~90 Gb worth of data, and aborted (as I didn't specify the -E option to btrfs send). Then, I retried with btrfs send -E 0, and it encountered the exact same error on the same file. > > # btrfs send -v /tank/backups/.snaps/incoming/sendme/ | pv 2>/dev/pts/23 | btrfs rec -E 0 /newfs/ > At subvol /tank/backups/.snaps/incoming/sendme/ > At subvol sendme > ERROR: failed to clone extents to retroarch/x86_64/cores/mednafen_saturn_libretro.dll: Invalid argument > ERROR: failed to clone extents to retroarch/x86_64/cores/mednafen_saturn_libretro.dll: Invalid argument This is probably the same case for which I sent a fix last week: https://patchwork.kernel.org/patch/11350129/ Thanks. > > The send/receive is still going on for now, currently around the ~200 Gb mark. > > Bees is running on this FS (but I stopped it before doing the send/receive). > > I can test patches if needed. > > -- > Stéphane. -- Filipe David Manana, “Whether you think you can, or you think you can't — you're right.”
