On Fri, 19 Jun 2020 at 09:24, Daniel Smedegaard Buus <danielbuus@xxxxxxxxx> wrote: > This seems ... well, wrong. Like, in, bug wrong. Surely, a single > block of bad data on a device shouldn't cause btrfs to produce such a > cascade of errors, making so much data inaccessible? > Oh, wait :D Wish my "cancel sending" timeout was longer on my email. Just realized the bug; me not using notrunc when "rotting" my loopback file. I essentially destroyed the entire loopback file from that sector til the end XD. That explains everything. Sorry for wasting your time :/
