<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Two for the price of one</title>
	<atom:link href="http://www.thestoragearchitect.com/2008/01/03/two-for-the-price-of-one/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thestoragearchitect.com/2008/01/03/two-for-the-price-of-one/</link>
	<description>Storage and Virtualisation</description>
	<lastBuildDate>Fri, 30 Jul 2010 18:12:37 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BarryWhyte</title>
		<link>http://www.thestoragearchitect.com/2008/01/03/two-for-the-price-of-one/comment-page-1/#comment-223</link>
		<dc:creator>BarryWhyte</dc:creator>
		<pubDate>Fri, 04 Jan 2008 22:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://thestoragearchitect.wordpress.com/2008/01/03/two-for-the-price-of-one/#comment-223</guid>
		<description>Chris,&lt;br/&gt;&lt;br/&gt;The beauty of the distributed nature of the &#039;chunks&#039; and hence the fast rebuild times (15mins) mean that as soon as one mirrored copy has been lost (single drive failure) a new second copy is made very soon afterwards. Most dual drive failures occur because of extra stress put on them due to the rebuild operation being performed. When this is targeted at the same disks that are already in a degraded state, recipe for disaster. The benefits are two fold due to the distributed nature. &lt;br/&gt;&lt;br/&gt;a) you don&#039;t put a much stress on any one set of drives (so are less likely to cause the second failure)&lt;br/&gt;&lt;br/&gt;b) as you suggested with a large enough distribution of drives the changes of a second drive failure causing both mirrored copies to be lost are less.&lt;br/&gt;&lt;br/&gt;I&#039;m looking at the lower level architecture and still trying to get my head round some of it too!</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>The beauty of the distributed nature of the &#8216;chunks&#8217; and hence the fast rebuild times (15mins) mean that as soon as one mirrored copy has been lost (single drive failure) a new second copy is made very soon afterwards. Most dual drive failures occur because of extra stress put on them due to the rebuild operation being performed. When this is targeted at the same disks that are already in a degraded state, recipe for disaster. The benefits are two fold due to the distributed nature. </p>
<p>a) you don&#8217;t put a much stress on any one set of drives (so are less likely to cause the second failure)</p>
<p>b) as you suggested with a large enough distribution of drives the changes of a second drive failure causing both mirrored copies to be lost are less.</p>
<p>I&#8217;m looking at the lower level architecture and still trying to get my head round some of it too!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
