Hacker News Reader

Comment by cake | Hacker News Reader

I wish there was something similar for SSDs.

There is, roughly. This is a lab test as opposed to production monitoring, but it is still interesting. Obviously SSDs and HDDs are quite different technically, so the appropriate test is quite different. They write data continuously to see how long they last.

We've now written over a petabyte, and only half of the SSDs remain. Three drives failed at different points—and in different ways—before reaching the 1PB milestone[1]

http://techreport.com/review/26523/the-ssd-endurance-experim...

Latest results: http://techreport.com/review/27062/the-ssd-endurance-experim...

Also worth looking at:

http://us.hardware.info/reviews/4178/10/hardwareinfo-tests-l...

Hardware.info did a "Write until it dies" test for a couple of 250GB Samsung SSDs last year. They found that the drive consistently exceeds the 1000 writes per cell spec.

After a few hundred drives, our anecdata is that failure over time on SSDs is generally related to drive endurance. Make sure you use a SMART utility which can read (and translate to English) the current net usage of the drive. Throw them away when you get to 100% usage.

I recently examined a set of Crucial m4s which were at 130% of usage. There was no lost data, but write bandwidth was hilariously bad (around 10-20MB/s).

It sounds like you might not have TRIM enabled? Or am I misunderstanding what you mean by 'usage'?

I'm talking about the "endurance" spec. Because Flash Memory can only be erased a finite number of times[1], SSD manufacturers specify the drive's endurance -- defined as the number of bytes which can be written to the SSD over its lifetime.

The SSDs helpfully keep track of how many bytes you've written and report that in the SMART info. For example, on my Windows dev system, HDD Guardian reports that I've used up 42% of my SSDs endurance (it's a Crucial m4 512GB). So by "usage", I mean the percentage of the endurance which has been burned.

[1] Each block of flash memory must be erased before it can be written. Each time you erase it, it "uses it up" a bit and will be harder to erase next time. So each time, the SSD controller is forced to erase it with just a bit more voltage. As the blocks become harder to erase, it takes more time to erase them and the SSD write bandwidth decreases.

That makes sense, thank you for explaining it to me.

Reply on news.ycombinator.com