<?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: EVA // Remaining space &amp;amp; Allocation Alarm Level in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656182#M35366</link>
    <description>You have "Disk drive failure protection" set to "Single".  This reserves the space equivalent to two phisical disks (2 x 279.39 GB). This space is reserved to perform rebuild in case a disk fails and cannot be used for vdisks.&lt;BR /&gt;&lt;BR /&gt;So you have (56 - 2)x 279.39 GB = 15087 GB available for vdisks. 95% of that is 14332.&lt;BR /&gt;&lt;BR /&gt;A vdisk in RAID 5 takes a 25% more space than in RAID 0 (EVA uses 4 data + 1 parity).&lt;BR /&gt;&lt;BR /&gt;So your calculations are correct, yes.</description>
    <pubDate>Fri, 02 Jul 2010 10:42:08 GMT</pubDate>
    <dc:creator>Víctor Cespón</dc:creator>
    <dc:date>2010-07-02T10:42:08Z</dc:date>
    <item>
      <title>EVA // Remaining space &amp; Allocation Alarm Level</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656181#M35365</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;I have a basic query on EVA space. Pls help me understand this.&lt;BR /&gt;&lt;BR /&gt;Let us consider an EVA 4000 2C4D array with 56 x 300 GB disks. Allocation Alarm Level in the Default Disk Group (the only Disk Group) is 95%.&lt;BR /&gt;&lt;BR /&gt;In this case,&lt;BR /&gt;&lt;BR /&gt;Raw capacity = 56 x 300 GB = 16800 GB&lt;BR /&gt;Formatted capacity = 56 x 279.39 GB = 15645.84 GB&lt;BR /&gt;In StorageWorks CvEVA &amp;gt; EVA Storage Network Properties, under Managed Storage System Capacity,&lt;BR /&gt;   Total = 15083 GB &amp;lt;- where's 562.84 GB&lt;BR /&gt;   Suppose 13736 GB is already allocated&lt;BR /&gt;   Then, remaining 1346 GB &amp;lt;- must be Vraid0&lt;BR /&gt;&lt;BR /&gt;If it is Vraid5, maximum size of the Vdisk is 1076 GB (which is about 80% of Vraid0 disk)&lt;BR /&gt;&lt;BR /&gt;My concern is - without triggering the Allocation Alarm, what is the maximum size that we can allocate to a new Vdisk. Here's my workout:-&lt;BR /&gt;&lt;BR /&gt;95% of 15083 GB = 14328.85 GB&lt;BR /&gt;Already allocated (in this case) = 13736 GB&lt;BR /&gt;&lt;BR /&gt;So, max allowable Vraid0 disk size = (14328.85 - 13736) = 592.85 GB&lt;BR /&gt;If we want a new Vraid5 disk, its maximum capacity can be 80% of 592.85 GB = 474.28 GB&lt;BR /&gt;&lt;BR /&gt;Pls correct me if I am wrong.</description>
      <pubDate>Fri, 02 Jul 2010 10:23:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656181#M35365</guid>
      <dc:creator>arkie</dc:creator>
      <dc:date>2010-07-02T10:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: EVA // Remaining space &amp; Allocation Alarm Level</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656182#M35366</link>
      <description>You have "Disk drive failure protection" set to "Single".  This reserves the space equivalent to two phisical disks (2 x 279.39 GB). This space is reserved to perform rebuild in case a disk fails and cannot be used for vdisks.&lt;BR /&gt;&lt;BR /&gt;So you have (56 - 2)x 279.39 GB = 15087 GB available for vdisks. 95% of that is 14332.&lt;BR /&gt;&lt;BR /&gt;A vdisk in RAID 5 takes a 25% more space than in RAID 0 (EVA uses 4 data + 1 parity).&lt;BR /&gt;&lt;BR /&gt;So your calculations are correct, yes.</description>
      <pubDate>Fri, 02 Jul 2010 10:42:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656182#M35366</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2010-07-02T10:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: EVA // Remaining space &amp; Allocation Alarm Level</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656183#M35367</link>
      <description>Thanks Vcespon for your immediate and informative response&lt;BR /&gt;&lt;BR /&gt;Can you also pls let me know if disk space reservation in case of Disk Drive Failure Protection set to None &amp;amp; Double ... are 0 and 4 respectively.&lt;BR /&gt;&lt;BR /&gt;EVA uses 4 data + 1 parity &amp;lt;&amp;lt; pls clarify this part&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Jul 2010 11:03:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656183#M35367</guid>
      <dc:creator>arkie</dc:creator>
      <dc:date>2010-07-02T11:03:44Z</dc:date>
    </item>
    <item>
      <title>Re: EVA // Remaining space &amp; Allocation Alarm Level</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656184#M35368</link>
      <description>Right, protection level NONE(or 0) does not reserve any space, but the EVA is still able to reconstruct redundancy if there is enough free space in the disk group. I would still not use NONE, because this prevents one from miscalculation.&lt;BR /&gt;And level double does indeed reserves 4 times the size of the largest disk drive in the group.&lt;BR /&gt;&lt;BR /&gt;4D+1P indicates how the EVA does VRAID-5 redundancy. It takes 4 Data chunks, calculates the Parity chunk and stores all five chunks on five different disk drives in the group so that any one disk drive can fail, but you do not have lost data.&lt;BR /&gt;&lt;BR /&gt;Well, at the low level it is a bit more complex, but the basic rule is 4D+1P on five different physical disk drives.&lt;BR /&gt;&lt;BR /&gt;Do not confuse the "5" in VRAID-5 with the "5" in "five disk drives". They are not related.&lt;BR /&gt;Other arrays do a RAID-5 with 3D+1P or 7D+1P or other values.</description>
      <pubDate>Fri, 02 Jul 2010 11:21:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656184#M35368</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-07-02T11:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: EVA // Remaining space &amp; Allocation Alarm Level</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656185#M35369</link>
      <description>Thanks Uwe, for the inputs &amp;amp; clarification</description>
      <pubDate>Fri, 02 Jul 2010 12:04:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-remaining-space-amp-allocation-alarm-level/m-p/4656185#M35369</guid>
      <dc:creator>arkie</dc:creator>
      <dc:date>2010-07-02T12:04:14Z</dc:date>
    </item>
  </channel>
</rss>

