George Crump


Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

SSD Failure Rates

Ever since SSD drives began their slow march to mainstream storage, there has been a constant chorus over concerns about SSD failure rates and questions on if the technology was ready for the enterprise. Most of the concern lies around how many writes a SSD drive can sustain. Vendors of enterprise SSD drives have gone to great lengths to make sure that today's SSD drives used in the data center will not have premature write issues. With the improvements in the quality of the NAND and the capabilities of the Flash controller, if the right vendor is selected, Flash SSDs should outlive most mechanical drives.

Although some are deserved, many of the concerns about SSD failure rates seems to come from personal experiences with consumer grade compact Flash, like those found in cameras or inexpensive thumb drives, which have had a sketchy past. Interestingly, if your personal experience was a mid-1990 RAM based SSD you would have the opposite reaction. RAM based SSDs have always proven to be extremely reliable. Flash is different. Its persistent storage state means that memory cells need to be written to. If the memory cell is full,, it needs to be erased and written over. The primary concern around Flash-based SSD is write endurance. In other words, how many write cycles can they handle? This typically is addressed in two ways. First by the type of SSD used and second by the intelligence on the controller. There are two types of Flash based technology: single level cell (SLC) and multi-level cell (MLC). Most MLC drives hold four states per cell, where SLC holds one state per cell. As a result MLC is higher capacity but more prone to failure, SLC is more expensive but also more reliable and have a much higher write endurance. Most enterprise drives are SLC based for this reason.

All Flash drives have a controller. The controller handles how data is written to the flash drive and it is one of the bigger differentiators of SSD quality. One of the controller's primary functions is to make sure that data is written evenly to each cell on the drive. This keeps a group of cells from wearing out before the other cells on the flash drive. The controller also manages excess cells on the drive, making those available as other cells wear out. The controller may even group the writes so that it can write larger blocks of data to the drive, which further helps with both performance and write longevity. The Flash controller technology has become so advanced that we are seeing a few vendors offer MLC based SSD drives to the enterprise. They can do this by leveraging all of the above controller technologies. While I'm not sure that MLC will replace SLC in the enterprise, we may see a tiering of SSD, just like we have today in hard drives.

While there are other factors in delivering reliable SSD technology the controller intelligence that the SSD supplier uses may be the key differentiator in reducing SSD failure rates. As we discuss in our article "Pay Attention to Flash Controllers when Comparing SSD Systems," it is reasonable to expect seven to ten years of life out of today's SSDs with the capabilities of today's controller technology, which is really beyond the life of any enterprise primary storage device.

Related Reading


More backup-recovery Insights



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers