<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: RAID 5 Is A Cruel Mistress</title>
	<atom:link href="http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/feed" rel="self" type="application/rss+xml" />
	<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/</link>
	<description>im in ur data centrz patchin ur serverz</description>
	<pubDate>Thu, 04 Dec 2008 19:06:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Ken Reiss</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-73810</link>
		<dc:creator>Ken Reiss</dc:creator>
		<pubDate>Tue, 26 Feb 2008 04:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-73810</guid>
		<description>I just ordered a Dell 2950 III with 5x 250 GB SATA in RAID 6.  Has anyone else done the same?

Any thoughts re: the performance degradation of RAID 6 vs. RAID 5?

Ken.</description>
		<content:encoded><![CDATA[<p>I just ordered a Dell 2950 III with 5x 250 GB SATA in RAID 6.  Has anyone else done the same?</p>
<p>Any thoughts re: the performance degradation of RAID 6 vs. RAID 5?</p>
<p>Ken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimmy</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-60928</link>
		<dc:creator>jimmy</dc:creator>
		<pubDate>Mon, 03 Dec 2007 12:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-60928</guid>
		<description>The new Dell PERC 6 controller can deal with RAID 6. The PERC 6 is shipping with 3rd gen 29** series</description>
		<content:encoded><![CDATA[<p>The new Dell PERC 6 controller can deal with RAID 6. The PERC 6 is shipping with 3rd gen 29** series</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44350</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 28 Sep 2007 03:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44350</guid>
		<description>We mitigate the risk on our critical systems using RAID 1 for the OS volume and RAID 5 for the other volumes. Each volume has a hot spare. Our SQL stuff is clustered with the databases/logs on a SAN which adds yet another layer of protection. The less critical stuff just uses RAID 1 or RAID 5 and we take our chances. In practice, it has worked well for us. We have survived two multi-drive failures this year alone. Of course, we are a smaller IT shop so we limit this strategy to systems that we define as "critical". That is, systems that are directly responsible for taking money in and getting product out the door. 

Another thing, HP's servers will generate a predictive drive failure warning and they will do a warranty replacement before the drive fails. This is has save by butt many, many times.</description>
		<content:encoded><![CDATA[<p>We mitigate the risk on our critical systems using RAID 1 for the OS volume and RAID 5 for the other volumes. Each volume has a hot spare. Our SQL stuff is clustered with the databases/logs on a SAN which adds yet another layer of protection. The less critical stuff just uses RAID 1 or RAID 5 and we take our chances. In practice, it has worked well for us. We have survived two multi-drive failures this year alone. Of course, we are a smaller IT shop so we limit this strategy to systems that we define as &#8220;critical&#8221;. That is, systems that are directly responsible for taking money in and getting product out the door. </p>
<p>Another thing, HP&#8217;s servers will generate a predictive drive failure warning and they will do a warranty replacement before the drive fails. This is has save by butt many, many times.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aharden</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44297</link>
		<dc:creator>aharden</dc:creator>
		<pubDate>Thu, 27 Sep 2007 17:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44297</guid>
		<description>Looks like Dell doesn't offer RAID 6 on either the PERC 5/i or the PERC 5/E.  This is a reason to consider HP.  I've never been a big fan of Dell's storage solutions.  They sometimes change OEMs (and as a result management tools and array configuration data) between generations, which kills consistency and increases data-loss risk on older arrays as older-generation support dries up.

We've deployed hundreds of servers (Dell and HP) and have found that multi-disk communications errors are much more likely to occur on external storage units than the built-in hot-plug storage bays of the tier 1 servers.</description>
		<content:encoded><![CDATA[<p>Looks like Dell doesn&#8217;t offer RAID 6 on either the PERC 5/i or the PERC 5/E.  This is a reason to consider HP.  I&#8217;ve never been a big fan of Dell&#8217;s storage solutions.  They sometimes change OEMs (and as a result management tools and array configuration data) between generations, which kills consistency and increases data-loss risk on older arrays as older-generation support dries up.</p>
<p>We&#8217;ve deployed hundreds of servers (Dell and HP) and have found that multi-disk communications errors are much more likely to occur on external storage units than the built-in hot-plug storage bays of the tier 1 servers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Plankers</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44240</link>
		<dc:creator>Bob Plankers</dc:creator>
		<pubDate>Thu, 27 Sep 2007 04:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44240</guid>
		<description>Excellent point. But how do you deal with that? Order another server at the same time, which will have drives from the same batch? Wait for two months until you get another batch?

To me it sounds like a mess. Maybe the way out of this is to keep as little data as possible... (pipe dream, I know). :-)</description>
		<content:encoded><![CDATA[<p>Excellent point. But how do you deal with that? Order another server at the same time, which will have drives from the same batch? Wait for two months until you get another batch?</p>
<p>To me it sounds like a mess. Maybe the way out of this is to keep as little data as possible&#8230; (pipe dream, I know). :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44238</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 27 Sep 2007 03:55:12 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44238</guid>
		<description>Another factor to consider is that many times the drives in these arrays are deployed at the same time and happen to be from the same manufacturing batch. An imperfection in a drive due to a manufacturing anomaly would likely apply to the entire batch and cause them to fail after similar usage.</description>
		<content:encoded><![CDATA[<p>Another factor to consider is that many times the drives in these arrays are deployed at the same time and happen to be from the same manufacturing batch. An imperfection in a drive due to a manufacturing anomaly would likely apply to the entire batch and cause them to fail after similar usage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wjl (Wolfgang Lonien)</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44110</link>
		<dc:creator>wjl (Wolfgang Lonien)</dc:creator>
		<pubDate>Tue, 25 Sep 2007 22:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44110</guid>
		<description>Distributed data is definitely the way to go. They do this for instance in hospitals I know, just in case that one building would burn down. In my last job with $ex_employer, we always sold two identical servers, configured as a HA cluster.

Of course, you need Gigabit Ethernet or even Fibre if you deal with lots of data.

cheers,
wjl</description>
		<content:encoded><![CDATA[<p>Distributed data is definitely the way to go. They do this for instance in hospitals I know, just in case that one building would burn down. In my last job with $ex_employer, we always sold two identical servers, configured as a HA cluster.</p>
<p>Of course, you need Gigabit Ethernet or even Fibre if you deal with lots of data.</p>
<p>cheers,<br />
wjl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Plankers</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44105</link>
		<dc:creator>Bob Plankers</dc:creator>
		<pubDate>Tue, 25 Sep 2007 21:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44105</guid>
		<description>That's a great point, and one that I didn't really consider. The problem is that once the controller marks a drive as dead it's pretty much "game over." A communications error also seems to be an argument for reducing the number of disks. The more there are the more chances of one of them causing a problem.

RAID 6 isn't an option on the Dell PERC5/i, which is the most common. Maybe the follow-on controllers in upcoming revisions of Dell servers will support RAID 6.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great point, and one that I didn&#8217;t really consider. The problem is that once the controller marks a drive as dead it&#8217;s pretty much &#8220;game over.&#8221; A communications error also seems to be an argument for reducing the number of disks. The more there are the more chances of one of them causing a problem.</p>
<p>RAID 6 isn&#8217;t an option on the Dell PERC5/i, which is the most common. Maybe the follow-on controllers in upcoming revisions of Dell servers will support RAID 6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aharden</title>
		<link>http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44103</link>
		<dc:creator>aharden</dc:creator>
		<pubDate>Tue, 25 Sep 2007 20:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2007/09/25/raid-5-is-a-cruel-mistress/#comment-44103</guid>
		<description>Some configurations support RAID 6, which uses two parity drives.  However, most of the double-drive failures I've seen involve failed communications between the RAID controller and the disks as opposed to two authentic drive failures occurring within a short window.

One thing I always recommend is a two-drive RAID 1 array dedicated to the OS and possibly applications.  Data should be housed on a separate array and everything should be backed up to another location.

On the 10k vs 15k issue, I use a mix of both in both the 2.5" and 3.5" form factors and haven't really seen a higher failure rate with 15k disks.</description>
		<content:encoded><![CDATA[<p>Some configurations support RAID 6, which uses two parity drives.  However, most of the double-drive failures I&#8217;ve seen involve failed communications between the RAID controller and the disks as opposed to two authentic drive failures occurring within a short window.</p>
<p>One thing I always recommend is a two-drive RAID 1 array dedicated to the OS and possibly applications.  Data should be housed on a separate array and everything should be backed up to another location.</p>
<p>On the 10k vs 15k issue, I use a mix of both in both the 2.5&#8243; and 3.5&#8243; form factors and haven&#8217;t really seen a higher failure rate with 15k disks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
