Regarding the SSD reliability discussion: this probably means nothing because sample size is so small, but anyway, FWIW: I've had two SSDs suddenly just die. That is, they become completely ivisible to the OS/BIOS. This is for my personal/home infrastructure, meaning the total number of SSDs I've had in my hands is less maybe a dozen or so. The two drives that died were cheapie Kingston drives, and very low-capacity at that. (One was a 16 GB drive; Kingston sent me a 64 GB drive for my warranty replacement. I think the other was maybe 32 GB, but I don't remember.) I don't recall their exact vintage, but they were old enough that their tiny capacity wasn't embarassing when purchased, but young enough to still be under warranty. At any rate, I have different but related question: does anyone have any thoughts with regards to using an SSD as a WORM (write-once, read-many) drive? For example, a big media collection in a home server. Ignoring the cost aspect, the nice thing about SSDs are their small size and neglible power consumption (and therefore low heat production). As mentioned previously in this thread, SSD at least removes the "mechanical" risks from a storage system. So what happens if you completely fill up an SSD, then never modify it after that, i.e. mount it read-only? I understand that the set bits in NAND memory slowly degrade over time, so it's clearly not true WORM media. But what kind of timescale might one expect before bit rot becomes a problem? And what if one were to use some kind of parity scheme (raid5/6, zfs, snapraid) to ocassionaly "refresh" the NAND memory? FWIW, I also asked about this on the ServeTheHome forums[1]. In general, seems there's a market for true WORM storage (but at SOHO prices of course!). Something like mdisc[2], but in modern mechanical-HDD capacities and prices. :) [1] http://forums.servethehome.com/hard-drives-solid-state-drives/2453-ssd-worm.html [2] http://www.mdisc.com/what-is-mdisc/ -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
