>>>>> "Dmitri" == Dmitri Nikulin <[email protected]> writes:
Dmitri> That's excellent, but until consumer-level drives have the same Dmitri> feature, the fact remains that consumer SSDs are a net loss in Dmitri> reliability compared to consumer rotating disks, My SSD testing has not been very promising in the data integrity department. I've got a couple of drives here which end up corrupting stuff every time they are reset or lose power. "Stuff" in this case is on the order of megabytes, not a few sectors like on spinning media. With disk drives the risk of garbling unrelated files is there but relatively small. On SSDs it's much higher because of the big blocking and the high latency erase/rewrite cycle. In several cases I've lost system binaries that obviously weren't being written when I crashed the system. In one case I even lost all of /sbin. Dmitri> I'm just curious if there's anything that can be done in a Dmitri> filesystem to minimise the damage of a lost eraseblock. The problem is that we have no way of knowing what's inside each erase block. We don't even know how big the erase block is. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
