<?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: regarding physical group in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611468#M825037</link>
    <description>See page 21 and 22 in the attached doc for more details.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sudeesh</description>
    <pubDate>Thu, 25 Aug 2005 04:32:40 GMT</pubDate>
    <dc:creator>Sudeesh</dc:creator>
    <dc:date>2005-08-25T04:32:40Z</dc:date>
    <item>
      <title>regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611463#M825032</link>
      <description>hai all&lt;BR /&gt;&lt;BR /&gt;pls help me to find out what is a physical groyp &lt;BR /&gt;&lt;BR /&gt;what is the differnce between a physical disk and physical group. what is the advantage of having physical group&lt;BR /&gt;&lt;BR /&gt;thanks in advance&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Aug 2005 02:19:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611463#M825032</guid>
      <dc:creator>Tvs</dc:creator>
      <dc:date>2005-08-25T02:19:42Z</dc:date>
    </item>
    <item>
      <title>Re: regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611464#M825033</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;When physical group is used to group say multiple physical disks while creating the volume group, physical links are maintained. This feature is useful while mirroring the drives. Drive extents will follow physical links as per PVGroup configuration. &lt;BR /&gt;&lt;BR /&gt;Following link may also be of help&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-90692/vgcreate.1M.html" target="_blank"&gt;http://docs.hp.com/en/B2355-90692/vgcreate.1M.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Mahesh</description>
      <pubDate>Thu, 25 Aug 2005 02:35:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611464#M825033</guid>
      <dc:creator>Mahesh Kumar Malik</dc:creator>
      <dc:date>2005-08-25T02:35:28Z</dc:date>
    </item>
    <item>
      <title>Re: regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611465#M825034</link>
      <description>pls helpme&lt;BR /&gt;1. how to create a physcial group&lt;BR /&gt;&lt;BR /&gt;2. what is the advantage using physical group instaed of physcial disk&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Aug 2005 02:42:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611465#M825034</guid>
      <dc:creator>Tvs</dc:creator>
      <dc:date>2005-08-25T02:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611466#M825035</link>
      <description>1) You can create PVGs directly editing the /etc/lvmpvg ascii file.&lt;BR /&gt;Here it is an example of the format:&lt;BR /&gt;&lt;BR /&gt;VG VG01&lt;BR /&gt;PVG PVG1&lt;BR /&gt;pv_path1&lt;BR /&gt;pv_path2&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;VG VG01&lt;BR /&gt;PVG PVG2&lt;BR /&gt;pv_path3&lt;BR /&gt;pv_path4&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;VG VG02&lt;BR /&gt;PVG PVG1&lt;BR /&gt;pv_path5&lt;BR /&gt;pv_path6&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;You can use the same name for PVG across different VGs, but not the same inside a VG&lt;BR /&gt;Be sure that the PVs owned by a PVG are owned by a VG.&lt;BR /&gt;&lt;BR /&gt;2) The advantages are for example a simpler management of displacing mirror copies for a LV only to PVs you want ( example: to the lvextend command you can specify a specific PVG )&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Alex</description>
      <pubDate>Thu, 25 Aug 2005 03:29:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611466#M825035</guid>
      <dc:creator>Alessandro Pilati</dc:creator>
      <dc:date>2005-08-25T03:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611467#M825036</link>
      <description>If there are multiple host bus adapters (SCSI or fibre channel) available on the system it is useful in terms of high availablility to have mirror copies located on different adapters. The strict allocation policy for mirrored LVs guarantees that the mirror copy will not be placed on the same disk but it could be placed on a disk that is on the same adapter. The latter case can be avoided by using physical volume groups. A PVG is a subset of PVs within a VG that can be defined using -p option of vgcreate/vgextend or simply by creating an ascii file called /etc/lvmpvg.&lt;BR /&gt;&lt;BR /&gt;Sudeesh&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Aug 2005 04:29:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611467#M825036</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2005-08-25T04:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611468#M825037</link>
      <description>See page 21 and 22 in the attached doc for more details.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sudeesh</description>
      <pubDate>Thu, 25 Aug 2005 04:32:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611468#M825037</guid>
      <dc:creator>Sudeesh</dc:creator>
      <dc:date>2005-08-25T04:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: regarding physical group</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611469#M825038</link>
      <description>I believe the biggest purpose of the PVGs was for extent based striping.  Once upon a time in order to to extent based striping you had to write a script that would allocate one extent from one disk, then mirror to another, then add another extent to the next disk, and mirror that, over and over and over ( ie. script the creation, and it took forever to build).  In late 10.20 HP added the -D option to lvcreate.  This required some type of grouping i.e. and the use of the -s g option.  -D (distributed stripe) -s g ( use strict groupings so overlap of mirrors and primaries did not occur).&lt;BR /&gt;&lt;BR /&gt;The extent based mirrored stripe ( psuedo raid 0+1, although the stripe size is now 4MB or the size of pesize) works great and is loads faster than concantenated volumes.  Pound for pound as fast as some array stripes in 0+1 without the cache assist.&lt;BR /&gt;&lt;BR /&gt;If you have local disks, use it.  Our typical config was two trays of DS2100 disk, 4 36GB drives in each, extent based stripe on the 4 mirrored to the other 4 in the other tray.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Aug 2005 09:23:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regarding-physical-group/m-p/3611469#M825038</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2005-08-25T09:23:05Z</dc:date>
    </item>
  </channel>
</rss>

