<?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: PVG x Stripe in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750508#M787477</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;      There is no direct bearing of PVG strict allocation on neither stripe created using "-i / -I" with lvcreate (block striping) nor the distruted allocation/Extent striping which is created with option "-D" with lvcreate command. The PVG strict allocation has direct bearing on Mirror allocation. &lt;BR /&gt; &lt;BR /&gt;      There is only one special case where this has a direct bearing on Striping. especially in extent stiping (-D) option. Thats because we have a case wherein we would be interested in mirroing the stiped volume. read the following quote from man page..&lt;BR /&gt;&lt;BR /&gt;QUOTE&lt;BR /&gt;&lt;BR /&gt;The distributed allocation policy REQUIRES the PVG-strict allocation policy ( -s g ) to ensure that mirrors of distributed extents do not overlap (for maximum availability).&lt;BR /&gt;&lt;BR /&gt;QUOTE END..&lt;BR /&gt;&lt;BR /&gt;      By defining a PVG group in /etc/lvmpvg, we define a logical group (Mind you LOGICAL) of the disks that are connected to different controller. By this, when we create a LV with the command "lvcreate" along with the options  "-m"(mirror)  and if "-s g" used to turn on "PVG strict allocation", the LVM subsystem will make sure the extents are choosen from the disks that belong to different PVG group.&lt;BR /&gt;&lt;BR /&gt;        So "PVG" group has only direct bearing with mirror allocation policy not with Striping.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Senthil Kumar .A&lt;BR /&gt;</description>
    <pubDate>Tue, 14 Mar 2006 07:37:01 GMT</pubDate>
    <dc:creator>Senthil Kumar .A_1</dc:creator>
    <dc:date>2006-03-14T07:37:01Z</dc:date>
    <item>
      <title>PVG x Stripe</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750506#M787475</link>
      <description>Hello people, how you doing?&lt;BR /&gt;&lt;BR /&gt;Can anyone tell me what's exactly the difference between PVG and Stripe?&lt;BR /&gt;&lt;BR /&gt;Another point, I've heard that the performance degrade when File System is created with stripe using meta disks stripe in the storage, is that true? Why?&lt;BR /&gt;&lt;BR /&gt;I hope that my english be understandable.&lt;BR /&gt;&lt;BR /&gt;Thank you very much&lt;BR /&gt;&lt;BR /&gt;André</description>
      <pubDate>Tue, 14 Mar 2006 06:56:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750506#M787475</guid>
      <dc:creator>Andre Augusto Ferreira</dc:creator>
      <dc:date>2006-03-14T06:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: PVG x Stripe</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750507#M787476</link>
      <description>PVG stripe - you form a group pvs and create lvol in that pv group. With pvg lvols, you can mirror. Use /etc/lvmpvg file and options -g to lvcreate.&lt;BR /&gt;&lt;BR /&gt;Strippping&lt;BR /&gt;Use of options -i and -I. you strip an lvol over the disks and you can choose the strip size. you can mirror a lvol created with -i and I options.&lt;BR /&gt;&lt;BR /&gt;Also, why would you want to strip twice. Depending upon the raid level you use, the disk coming from SAN/NAS is already stripped. So strippping it again, is not going to help and may even add to slower response and system overhead.</description>
      <pubDate>Tue, 14 Mar 2006 07:17:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750507#M787476</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2006-03-14T07:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: PVG x Stripe</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750508#M787477</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;      There is no direct bearing of PVG strict allocation on neither stripe created using "-i / -I" with lvcreate (block striping) nor the distruted allocation/Extent striping which is created with option "-D" with lvcreate command. The PVG strict allocation has direct bearing on Mirror allocation. &lt;BR /&gt; &lt;BR /&gt;      There is only one special case where this has a direct bearing on Striping. especially in extent stiping (-D) option. Thats because we have a case wherein we would be interested in mirroing the stiped volume. read the following quote from man page..&lt;BR /&gt;&lt;BR /&gt;QUOTE&lt;BR /&gt;&lt;BR /&gt;The distributed allocation policy REQUIRES the PVG-strict allocation policy ( -s g ) to ensure that mirrors of distributed extents do not overlap (for maximum availability).&lt;BR /&gt;&lt;BR /&gt;QUOTE END..&lt;BR /&gt;&lt;BR /&gt;      By defining a PVG group in /etc/lvmpvg, we define a logical group (Mind you LOGICAL) of the disks that are connected to different controller. By this, when we create a LV with the command "lvcreate" along with the options  "-m"(mirror)  and if "-s g" used to turn on "PVG strict allocation", the LVM subsystem will make sure the extents are choosen from the disks that belong to different PVG group.&lt;BR /&gt;&lt;BR /&gt;        So "PVG" group has only direct bearing with mirror allocation policy not with Striping.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Senthil Kumar .A&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Mar 2006 07:37:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pvg-x-stripe/m-p/3750508#M787477</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2006-03-14T07:37:01Z</dc:date>
    </item>
  </channel>
</rss>

