<?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: 3PAR in HPE 3PAR StoreServ Storage</title>
    <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003821#M4225</link>
    <description>&lt;P&gt;Hello Customer,&lt;/P&gt;&lt;P&gt;Set Size – The number of chunklets in a Raid Set.&amp;nbsp;&amp;nbsp; Logical drives are organized in rows of RAID sets. The set size is the number of sets within a row and serves a different purpose depending upon the RAID technology type:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Examples (Note: these are not all the Raid Geometries and hence set sizes supported):&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Raid 1 (1 + 1) has a set size of 2, one data chunklet and one copy chunklet&lt;/P&gt;&lt;P&gt;Raid 5 (3 + 1) has a set size of 4, three data chunklets and one parity chunklet*&lt;/P&gt;&lt;P&gt;Raid 6 (6 + 2) has a set size of 8, six data chunklets and two parity chunklets*&lt;/P&gt;</description>
    <pubDate>Wed, 25 Apr 2018 11:57:27 GMT</pubDate>
    <dc:creator>Haitao_Zhang</dc:creator>
    <dc:date>2018-04-25T11:57:27Z</dc:date>
    <item>
      <title>3PAR</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7001734#M4118</link>
      <description>&lt;P&gt;&lt;BR /&gt;3PAR 7200&lt;/P&gt;&lt;P&gt;explain what is CPG set size and what does it affect how to calculate?&lt;BR /&gt;what is the default set size choose for Raid 5 Raid 6?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 06 Apr 2018 11:49:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7001734#M4118</guid>
      <dc:creator>hdzen</dc:creator>
      <dc:date>2018-04-06T11:49:02Z</dc:date>
    </item>
    <item>
      <title>Re: 3PAR</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7001959#M4120</link>
      <description>&lt;P&gt;The CPG set size is the total of data and parity chunkets in each RAIDset that contributes to the CPG's storage.&lt;BR /&gt;Read the &lt;STRONG&gt;HPE 3PAR StoreServ Storage Concepts Guide&lt;/STRONG&gt;. You can find it and other 3PAR documentation at the &lt;STRONG&gt;Hewlett Packard Enterprise Information Library&lt;/STRONG&gt; (&lt;A href="http://www.hpe.com/info/storage/docs" target="_blank"&gt;http://www.hpe.com/info/storage/docs&lt;/A&gt;).&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2018 15:27:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7001959#M4120</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2018-04-09T15:27:11Z</dc:date>
    </item>
    <item>
      <title>Re: 3PAR</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003583#M4186</link>
      <description>&lt;P&gt;Dear Customer,&lt;/P&gt;&lt;P&gt;CPG isn't a container that has your volumes are in, it's not like a pool that you give disk space too, a CPG is just a template to say how you would like your volumes to be configured, so the space you see listed against the CPG is just the amount of space volumes are using that are using that CPGs template.&lt;/P&gt;&lt;P&gt;The CPG should automatically grow but it depends on which metric you are looking at for the free space. In some cases it can be that the CPG parameters are set in such a way that some of the space isn't by default available to that CPG e.g. you are enforcing cage level availability at the CPG and the CPG can't maintain that level of availability on the remaining free space in a given drive class.&lt;/P&gt;&lt;P&gt;If you do a 'cli% showspace -cpg *' that should list the CPG's, under EstFree column you'll see LDFree for the given CPG, divide that number by 1024 and it should provide the free space in GiB available to that CPG based on its current growth parameters. You can get the same from the CPG properties in the GUI.&lt;/P&gt;&lt;P&gt;The output of the following would be helpful for you to understand the space available:&lt;/P&gt;&lt;P&gt;"showsys -space"&lt;BR /&gt;"showcpg -space"&lt;BR /&gt;"showcpg -sdg"&lt;/P&gt;&lt;P&gt;Remember the CPG's in most cases will compete for the same space on the back end disks as such they grow based only on demand. Take a look at the concepts guide from page 43:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04204225-6&amp;amp;lang=en-us&amp;amp;cc=us&amp;amp;docLocale=en_US" target="_blank"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04204225-6&amp;amp;lang=en-us&amp;amp;cc=us&amp;amp;docLocale=en_US&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I am an HPE Employee&lt;BR /&gt;If this helps you with your issue, please click the thumb to register a Kudo.&lt;BR /&gt;If it resolves the issue, please consider marking it as an Accepted Solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 15:35:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003583#M4186</guid>
      <dc:creator>Venkatesh_SL</dc:creator>
      <dc:date>2018-04-24T15:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: 3PAR</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003784#M4215</link>
      <description>&lt;P&gt;Hello Customer&lt;/P&gt;&lt;P&gt;The Number of chunkets on a given RIAD Set is called setsize.&lt;/P&gt;&lt;P&gt;Ifor Example, RAID 5 with 3+1&amp;nbsp; will have set size of 4 means 3 data and 1 parity.&lt;/P&gt;&lt;P&gt;Likewise for any of the RAID combinations.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;BR /&gt;Vibeesh V&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 09:05:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003784#M4215</guid>
      <dc:creator>vibeesh1</dc:creator>
      <dc:date>2018-04-25T09:05:48Z</dc:date>
    </item>
    <item>
      <title>Re: 3PAR</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003815#M4223</link>
      <description>&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;Find here the different combination of RAIDSet used for Raid 5 and RAID 6 for software version 3.3.1&lt;/P&gt;&lt;P&gt;–RAID 5 from 3 (2D+1P) to 9 (8D+1P)&lt;/P&gt;&lt;P&gt;–RAID 6 at&amp;nbsp; 6 (4D+2P), 8 (6D+2P), 10 (8D+2P), 12 (10D+2P) or 16 (14D+2P)&lt;/P&gt;&lt;P&gt;–RAID 5 uses a set size (SSZ) of 4 (3D+1P) by default&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 11:31:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003815#M4223</guid>
      <dc:creator>Wassim_SV</dc:creator>
      <dc:date>2018-04-25T11:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: 3PAR</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003821#M4225</link>
      <description>&lt;P&gt;Hello Customer,&lt;/P&gt;&lt;P&gt;Set Size – The number of chunklets in a Raid Set.&amp;nbsp;&amp;nbsp; Logical drives are organized in rows of RAID sets. The set size is the number of sets within a row and serves a different purpose depending upon the RAID technology type:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Examples (Note: these are not all the Raid Geometries and hence set sizes supported):&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Raid 1 (1 + 1) has a set size of 2, one data chunklet and one copy chunklet&lt;/P&gt;&lt;P&gt;Raid 5 (3 + 1) has a set size of 4, three data chunklets and one parity chunklet*&lt;/P&gt;&lt;P&gt;Raid 6 (6 + 2) has a set size of 8, six data chunklets and two parity chunklets*&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 11:57:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/3par/m-p/7003821#M4225</guid>
      <dc:creator>Haitao_Zhang</dc:creator>
      <dc:date>2018-04-25T11:57:27Z</dc:date>
    </item>
  </channel>
</rss>

