<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EVA3000 with mixed drive types in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva3000-with-mixed-drive-types/m-p/3519271#M15757</link>
    <description>You may want to create an official support case for this. The numbers sound a little out of whack. The system is not still actively rebalancing/leveling (or some such)? Gave it enough time to settle?&lt;BR /&gt;&lt;BR /&gt;Just today someone posted an Eva best practices document in the hpux forum: &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=850958" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=850958&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Is this because there is a mix of two types of disks in this DG?&lt;BR /&gt;&lt;BR /&gt;The document attached to the above suggest that the Eva nicely incorporates all the space. I quote:&lt;BR /&gt;"The EVA will attempt to ensure that the amount on each physical disk drive is proportional to that driveâ  s contribution to the overall capacity. This means that larger drives will have more data on them than smaller drives. As an example, a 72 GB disk will have twice as much user data on it as a 36 GB drive. In a random access type of application, this implies that the larger drives will have twice as much I/O as the smaller drives, resulting in an I/O load imbalance at the disk drive level."&lt;BR /&gt;&lt;BR /&gt;Hope this helps a little....&lt;BR /&gt;&lt;BR /&gt;Hei</description>
    <pubDate>Wed, 06 Apr 2005 20:12:56 GMT</pubDate>
    <dc:creator>Hein van den Heuvel</dc:creator>
    <dc:date>2005-04-06T20:12:56Z</dc:date>
    <item>
      <title>EVA3000 with mixed drive types</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-with-mixed-drive-types/m-p/3519270#M15756</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Case: EVA3000 historical configuration with a number of 72 GB disks and a number of 300GB add-on disks in the default DG.&lt;BR /&gt;With Command View I can check the default DG.&lt;BR /&gt;I have a raw capacity for this DG of appr. 1900GB and a total storage space of ~1250GB (net available). The storage space used is appr. 550GB, so actual available space is ~700GB.&lt;BR /&gt;The disk group properties say:&lt;BR /&gt;Occupancy: 550GB, failure prot. single&lt;BR /&gt;This is clear and looks OK for sparing level setting etc.&lt;BR /&gt;&lt;BR /&gt;Strange thing is the following:&lt;BR /&gt;In the diskgroup properties there is also:&lt;BR /&gt;Total capacity: 1241GB&lt;BR /&gt;available:&lt;BR /&gt;Vraid0 362GB&lt;BR /&gt;Vraid1 181GB&lt;BR /&gt;Vraid5 182GB&lt;BR /&gt;&lt;BR /&gt;When creating a new vdisk I cannot go greater than this 362GB for a Vraid0 disk while ~700GB is available.&lt;BR /&gt;Can anyone explain this? Is this because there is a mix of two types of disks in this DG?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Philip&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Apr 2005 10:51:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-with-mixed-drive-types/m-p/3519270#M15756</guid>
      <dc:creator>Ph. Leenman</dc:creator>
      <dc:date>2005-04-06T10:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: EVA3000 with mixed drive types</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva3000-with-mixed-drive-types/m-p/3519271#M15757</link>
      <description>You may want to create an official support case for this. The numbers sound a little out of whack. The system is not still actively rebalancing/leveling (or some such)? Gave it enough time to settle?&lt;BR /&gt;&lt;BR /&gt;Just today someone posted an Eva best practices document in the hpux forum: &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=850958" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=850958&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Is this because there is a mix of two types of disks in this DG?&lt;BR /&gt;&lt;BR /&gt;The document attached to the above suggest that the Eva nicely incorporates all the space. I quote:&lt;BR /&gt;"The EVA will attempt to ensure that the amount on each physical disk drive is proportional to that driveâ  s contribution to the overall capacity. This means that larger drives will have more data on them than smaller drives. As an example, a 72 GB disk will have twice as much user data on it as a 36 GB drive. In a random access type of application, this implies that the larger drives will have twice as much I/O as the smaller drives, resulting in an I/O load imbalance at the disk drive level."&lt;BR /&gt;&lt;BR /&gt;Hope this helps a little....&lt;BR /&gt;&lt;BR /&gt;Hei</description>
      <pubDate>Wed, 06 Apr 2005 20:12:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva3000-with-mixed-drive-types/m-p/3519271#M15757</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2005-04-06T20:12:56Z</dc:date>
    </item>
  </channel>
</rss>

