<br><br><div class="gmail_quote">On Mon, Aug 16, 2010 at 12:29 AM, Florin Iucha <span dir="ltr"><<a href="mailto:florin@iucha.net">florin@iucha.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Sun, Aug 15, 2010 at 02:26:06PM -0500, Robert Nesius wrote:<br>
<br>
What? If I ask "get this on the platter", it better be on a platter,<br>
not in the cache of some smart-less drive, waiting for the power<br>
failure.<br></blockquote><div><br>I think you missed my point here. I was talking about writes, not reads, btw. <br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
> That's assuming you didn't match cache<br>
> sizes, which most people likely would have the sense to not do even if they<br>
> were mixing/matching drives/vendors.<br>
<br>
I'm not sure what you mean here.<br></blockquote><div><br>Yep, you missed it. But my example here is... not a big deal. The larger point has already been said better by someone else - drives from different manufacturers are not guaranteed to behave precisely the same way. That matters more for some RAID types than others I guess.<br>
<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
> My experience in large-enterprise installs is that everyone uses the same<br>
> drives within their arrays and disk cabinets.<br>
<br>
My experience with large-scale restaurant operations is that the food<br>
is crap. </blockquote><div><br>I'm talking about large-enterprise computing. Not restaurants. <br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
What would happen to an admin if 3 out of the 6 drives in a<br>
cabinet fail? </blockquote><div><br>The cabinets I'm used to have 350+ spindles so ... probably not much. <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
What would happen to the manager who signed the<br>
purchase order for 12 identical drives? </blockquote><div><br>Why should anything happen to him? <br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Nothing -- failure has no<br>
consequences. (I am ignoring the 'find the tape and restore the<br>
stuff'. Downtime is real money, it must come from somewhere.)<br></blockquote><div><br>If a drive fails in the woods and no one sees it, is data actually lost? <br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
> Lastly, diversifying drive as a risk-mitigation strategy can have the<br>
> opposite effect - one of the mix-in products may be far worse than the<br>
> others.<br>
<br>
So you'd rather have 6 identical crappy drives, or a prayer's chance<br>
that at least half are good?</blockquote><div><br>I'd rather have six good drives versus a stronger assurance of 3 bad drives. If my quality metrics show a statistically significantly higher failure rate for the brand I'm using, I'll try a different one. <br>
<br>Btw, let's say you have 10,000 spindles going... are you going to make sure every cabinet, every drawer, and every array is going to have the same mix/distribution of drives from different vendors? <br><br>But even talking about just apples (a raid array with six drives) versus oranges (10,000 spindles) I'd still be inclined to keep the hardware the same as much as possible. But maybe in a domain with that few spindles it makes sense to diversify. The thought had never crossed my mind before - that's why I asked what people thought. <br>
<br>-Rob <br></div></div>