[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Tue, 13 Dec 2005 16:30:07 -0400 -->
- <!--x-from-r13: uoof ng pbzpnfg.arg (Xrss Vhoof) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Linux support for Intel Matrix Storage Manager? -->
- <li><em>date</em>: Tue, 13 Dec 2005 16:30:07 -0400</li>
- <li><em>from</em>: hbbs at comcast.net (Jeff Hubbs)</li>
- <li><em>in-reply-to</em>: <<a href="msg00158.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00158.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] Linux support for Intel Matrix Storage Manager?</li>
I've developed a pet peeve since disk drives started going beyond 9GB or
so. I don't like splitting up individual physical disk drives into
matching sets of partitions so that I can make RAID volumes across
corresponding partitions on the various drives. Why? Because if one
partition on one drive develops a bad block, I have to disrupt healthy
(and potentially more critical) RAID volumes when I pull the drive with
the bad block, and I have to endure degraded disk I/O while ALL the RAID
volumes rebuild at once when I put the replacement drive in.
This is why I wish that the industry would still produce 2, 4, and 8GB
drives that are just butt-fast and butt-reliable. It seems to me that
the dot-com-boom drive to sell 1U and 2U servers forced these two- and
four-drive configurations on the world had a lot to do with making
multiple RAID volumes across the same set of drives a common practice.
That, and WinNT's default "C Drive = Only Drive" combined with admins
who had never before dealt with multi-disk/RAID systems and how you can
use different kinds of drives and RAID levels to optimize a machine for
what it's going to be doing.
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00160" href="msg00160.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
<li><strong><a name="00161" href="msg00161.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
<ul><li><em>From:</em> meuon at geeklabs.com (Mike Harrison)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00158" href="msg00158.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
<ul><li><em>From:</em> rekoil at semihuman.com (Chris Woodfield)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00158.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00160.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00158.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00160.html">[ale] Linux support for Intel Matrix Storage Manager?</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00159"><strong>Date</strong></a></li>
<li><a href="threads.html#00159"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>