<?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 Time to Expand an Array in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272647#M12084</link>
    <description>I have a 3x72Gb raid 5 array in a ML350G3 which I have added a forth 72Gb drive to.  I have set the controller configuration so that the priority on expanding the array is set to high.  How long should it take as I started it on Saturday morning and it is now Tuesday and it is still expanding.</description>
    <pubDate>Mon, 10 May 2004 22:52:09 GMT</pubDate>
    <dc:creator>Andrew McLean_2</dc:creator>
    <dc:date>2004-05-10T22:52:09Z</dc:date>
    <item>
      <title>Time to Expand an Array</title>
      <link>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272647#M12084</link>
      <description>I have a 3x72Gb raid 5 array in a ML350G3 which I have added a forth 72Gb drive to.  I have set the controller configuration so that the priority on expanding the array is set to high.  How long should it take as I started it on Saturday morning and it is now Tuesday and it is still expanding.</description>
      <pubDate>Mon, 10 May 2004 22:52:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272647#M12084</guid>
      <dc:creator>Andrew McLean_2</dc:creator>
      <dc:date>2004-05-10T22:52:09Z</dc:date>
    </item>
    <item>
      <title>Re: Time to Expand an Array</title>
      <link>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272648#M12085</link>
      <description>Andrew,&lt;BR /&gt;I have read something about 15 minutes per GigaByte on an otherwise idle controller.</description>
      <pubDate>Tue, 11 May 2004 02:17:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272648#M12085</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-05-11T02:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: Time to Expand an Array</title>
      <link>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272649#M12086</link>
      <description>Thanks for that, given that the disk is hardly idle, I should expect it to take a few more days.  I assume that the 15min per Gb is pysical size of the hard disk and not the amount of data currently stored on the disk. Thanks again.</description>
      <pubDate>Tue, 11 May 2004 02:24:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272649#M12086</guid>
      <dc:creator>Andrew McLean_2</dc:creator>
      <dc:date>2004-05-11T02:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: Time to Expand an Array</title>
      <link>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272650#M12087</link>
      <description>Sure, RAID controllers present a list of logical blocks to the host - they don't have an idea of what a filesystem is. Some advanced controllers like the EVA maintain a map of which 'segments' of a virtual disk have data written to and use this knowlege to optimize replication or snapclones, but that does require additional ressources in the system.</description>
      <pubDate>Tue, 11 May 2004 02:44:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/time-to-expand-an-array/m-p/3272650#M12087</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-05-11T02:44:52Z</dc:date>
    </item>
  </channel>
</rss>

