<?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 confuse about PV group in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/confuse-about-pv-group/m-p/3933223#M287673</link>
    <description>dear all,&lt;BR /&gt;i have never deal with PV group,so what is its benifit? and how to create PV group and how to maintance? is there any document about PV group?&lt;BR /&gt;&lt;BR /&gt;thanks a lot</description>
    <pubDate>Fri, 26 Jan 2007 02:38:18 GMT</pubDate>
    <dc:creator>stephen peng</dc:creator>
    <dc:date>2007-01-26T02:38:18Z</dc:date>
    <item>
      <title>confuse about PV group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/confuse-about-pv-group/m-p/3933223#M287673</link>
      <description>dear all,&lt;BR /&gt;i have never deal with PV group,so what is its benifit? and how to create PV group and how to maintance? is there any document about PV group?&lt;BR /&gt;&lt;BR /&gt;thanks a lot</description>
      <pubDate>Fri, 26 Jan 2007 02:38:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/confuse-about-pv-group/m-p/3933223#M287673</guid>
      <dc:creator>stephen peng</dc:creator>
      <dc:date>2007-01-26T02:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: confuse about PV group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/confuse-about-pv-group/m-p/3933224#M287674</link>
      <description>(Hmm... you have assigned points to only about half of the answers to your questions. Please assign points, it helps others to find out the *best* solutions if they are having similar problems.)&lt;BR /&gt;&lt;BR /&gt;A physical volume group (PVG) is  a level of organization between physical volumes (PVs) and volume groups (VGs). The PVG names must be unique within a volume group, but the same PVG name can be reused in a different VG. It's useful when you have e.g. four or more disks on two SCSI buses, and want to make a mirrored volume group out of them with MirrorDisk.&lt;BR /&gt;&lt;BR /&gt;Normally, the LVM system considers all four PVs as equals. So, it will place the mirror copy on the next available PV - which, in this case, might be on the same SCSI bus as the first copy. This is bad both performance- and reliability-wise, so you'll want to avoid that.&lt;BR /&gt;&lt;BR /&gt;In a setup like this, it's recommended that you group the PVs into PVGs, so that each PVG will contain all the PVs on a single SCSI bus. Then you can set the mirror allocation policy of each LV to "PVG-strict" (lvcreate/lvchange -s g).&lt;BR /&gt;&lt;BR /&gt;When the allocation policy is "PVG-strict", the MirrorDisk will automatically place the mirror copy of a LV onto a different PVG than the original... so both SCSI buses get used in parallel.&lt;BR /&gt;&lt;BR /&gt;When creating or extending a VG, you can use the "-g" option to add the new PV to a designated PVG within that VG. If the PVG does not exist yet, it will be created automatically.&lt;BR /&gt;&lt;BR /&gt;You can also set up the PVGs manually by creating the /etc/lvmpvg file (or editing it,  if it exists). You must be very careful if you do that. See "man lvmpvg" for details.&lt;BR /&gt;&lt;BR /&gt;When you have PVGs set up for a VG, you could also use "distributed" extent allocation policy (lvcreate -D y) on LVs of that VG. It's sort of equivalent to striping, but stripe size is equal to the extent size. The standard striping option (lvcreate -i) is more finely-grained and is likely to produce better performance.</description>
      <pubDate>Fri, 26 Jan 2007 03:57:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/confuse-about-pv-group/m-p/3933224#M287674</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-01-26T03:57:04Z</dc:date>
    </item>
  </channel>
</rss>

