You can't always use the correct eraseblock size with BCache, since it doesn't (didn't, at least at the time I created my cache) support non-powers-of-two that TLC drives use. That said, TRIM is not supposed to blow away entire eraseblocks, just let the drive know the mapping between presented LBA and internal address is no longer needed, allowing it to do what it wishes with that knowledge (generally reclaim multiple partial blocks to create fully empty blocks). I can't find any reports of errors with TRIM support in the 840-EVO series. They had/may still have a problem reading old data that was a big deal in the fall, and there was an 850 firmware that bricked some drives. Nothing about TRIM erasing unintended data, though. There were no problems with bcache at all in the year+ I've used it, until I enabled bcache discard. Before that, I put on over 100 terabytes of writes to the bcache partition with no interface errors. I've also never seen a TRIM failure in other filesystems using the same model in my other systems. There was no powerloss, the system went through a software reboot cycle before the failure. I'm therefore *extremely* hesitant about allowing this to be written off as a hardware failure. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
