> You can run 'slabtop' while doing the send operation. > That might be enough. > > It's very likely the backreference walking code, due to huge ulists > (kmalloc-N slab), lots of btrfs_prelim_ref structures > (btrfs_prelim_ref slab), etc. I actually did run slabtop once but couldn't remember the exact name of the top entry, so I didn't mention it. Now that you mentioned the options though, I'm pretty sure it was kmalloc-N. N was probably 64 but that I'm not sure about. > Yes, it's likely a different bug. I don't think it's related either. I have only seen these warnings after the bug triggered though, reading the file under normal conditions doesn't produce them. What would be the best way to get more information on how btrfs comes to the conclusion that this file is corrupt? > Ideally yes. But that's a lot harder to do for several reasons and in > the end might not be worth it. I see, thanks! -Atemu
