<?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>Operating System - HP-UXのトピックRe: vgextend problem</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438934#M6493</link>
    <description>1) pvcreate -f /dev/rdsk/(c2t6d0) this in bracket is your disk hard ware path you can find your harddisk by doing ioscan.&lt;BR /&gt;2) vgextend /dev/vgxx/dev/dsk/c2t6d0&lt;BR /&gt;3)lvextend -L size of volgroup /dev/vgxx/lvxx&lt;BR /&gt;4)extendfs -F vxfs /dev/vgxx/rlvolxx&lt;BR /&gt;&lt;BR /&gt;after doing all this then mount your file system back again.&lt;BR /&gt;substitute xx with your vggroup and logical volumes.</description>
    <pubDate>Mon, 28 Aug 2000 13:13:07 GMT</pubDate>
    <dc:creator>Cisco</dc:creator>
    <dc:date>2000-08-28T13:13:07Z</dc:date>
    <item>
      <title>vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438921#M6480</link>
      <description>Dear all,&lt;BR /&gt;&lt;BR /&gt; I am extending a VG by adding a new disk&lt;BR /&gt;&lt;BR /&gt; to increase the FREE PE's (increase free&lt;BR /&gt; space) on the VG.&lt;BR /&gt;&lt;BR /&gt; After doing the vgextend also the vgdisplay&lt;BR /&gt; shows the same FREE PE's as before vgextend.&lt;BR /&gt;&lt;BR /&gt;  Is any one Know the solution?&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Aug 2000 09:36:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438921#M6480</guid>
      <dc:creator>R.Mahendran_1</dc:creator>
      <dc:date>2000-08-23T09:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438922#M6481</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Did you execute pvcreate to prepare the physical volume for use in LVM?&lt;BR /&gt;&lt;BR /&gt;Bye,&lt;BR /&gt;Rik</description>
      <pubDate>Wed, 23 Aug 2000 09:43:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438922#M6481</guid>
      <dc:creator>RikTytgat</dc:creator>
      <dc:date>2000-08-23T09:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438923#M6482</link>
      <description>I know its the cheats way but pvcreate it through sam and add it to the VG it will be easier, when you do a vgdisplay -v does the new disk show up as being in the VG ????</description>
      <pubDate>Wed, 23 Aug 2000 09:51:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438923#M6482</guid>
      <dc:creator>Scott Dunkley</dc:creator>
      <dc:date>2000-08-23T09:51:43Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438924#M6483</link>
      <description>The TOTAL PE field from vgdisplay should also have increased when you added in a new disk. Did it ? If not then the new disk didnt add into the volume group - if you do a vgdisplay -v | grep "PV Name"  does it show the disk you added in ?</description>
      <pubDate>Wed, 23 Aug 2000 09:59:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438924#M6483</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2000-08-23T09:59:10Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438925#M6484</link>
      <description>Did you got a message after vgextend saying the "Volume group is successfully extended". &lt;BR /&gt;Try doing a "vgchane -a y /dev/vg??" after vgextend.&lt;BR /&gt;If yes then do a "strings /etc/lvmtab" and see if you can see the disk i.e.(/dev/dsk/c?t?d?) under the Volume group. For ex.&lt;BR /&gt;"/etc/lvmtab:"&lt;BR /&gt;/dev/vg??&lt;BR /&gt;/dev/dsk/c?t?d?&lt;BR /&gt;Also do a "vgdisplay -v /dev/vg?? | grep PV" name.&lt;BR /&gt;If still things doesn't work then i suggest you put the vg details and command you used to configure the disk.</description>
      <pubDate>Wed, 23 Aug 2000 10:19:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438925#M6484</guid>
      <dc:creator>Vincente Fernandes</dc:creator>
      <dc:date>2000-08-23T10:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438926#M6485</link>
      <description>Did you extend the filesystems? If not do lvextend -L NNN /dev/vgnn/lvoln;&lt;BR /&gt;then extendfs -F (filesystem) /dev/vgnn/rlvoln</description>
      <pubDate>Wed, 23 Aug 2000 10:19:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438926#M6485</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-08-23T10:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438927#M6486</link>
      <description>Rename /etc/fstab and run vgscan.&lt;BR /&gt;Did you extend the filesystems? If not do lvextend -L NNN /dev/vgnn/lvoln;&lt;BR /&gt;then extendfs -F (fsytyp) /dev/vgnn/rlvoln</description>
      <pubDate>Wed, 23 Aug 2000 10:20:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438927#M6486</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-08-23T10:20:31Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438928#M6487</link>
      <description>Chris,&lt;BR /&gt;&lt;BR /&gt;Rename the /etc/fstab? You mean /etc/lvmtab, then run vgscan.</description>
      <pubDate>Wed, 23 Aug 2000 13:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438928#M6487</guid>
      <dc:creator>Cheryl Griffin</dc:creator>
      <dc:date>2000-08-23T13:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438929#M6488</link>
      <description>Check with "vgdisplay -v" if you have got PV-links - then the FREE PEs wont change.&lt;BR /&gt;Remove your ?/etc/lvmtab" and re-create it with "vgscan" (see man-page first).&lt;BR /&gt;Then do the "vgdisplay -v" and tell us the output.&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Aug 2000 21:15:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438929#M6488</guid>
      <dc:creator>Wodisch</dc:creator>
      <dc:date>2000-08-24T21:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438930#M6489</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;Tought you might need this..when extending volume group from a new disk&lt;BR /&gt;1. ioscan -fnC &lt;DISK&gt; = to determine the device file of the disk.&lt;BR /&gt;2.  pvcreate /dev/rdsk/c1t5d0 = (the device file depends on the results of #1.)  If there are errors that the disk contains some LVM information,  try pvcreate -f /dev/rdsk/c1t5d0.&lt;BR /&gt;3.  vgextend /dev/vg01 /dev/dsk/c1t5d0 = The volume group has additional free PEs now.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Joey&lt;/DISK&gt;</description>
      <pubDate>Thu, 24 Aug 2000 21:20:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438930#M6489</guid>
      <dc:creator>Kurtkarl</dc:creator>
      <dc:date>2000-08-24T21:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438931#M6490</link>
      <description>Dependeing upon the your configuration, there is a maximum amount of PE's that can be in a VG which if I recall correctly is 25535.&lt;BR /&gt;&lt;BR /&gt;And like the MAXPV's, cannot be changed on the fly.</description>
      <pubDate>Fri, 25 Aug 2000 12:55:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438931#M6490</guid>
      <dc:creator>Vince Inman</dc:creator>
      <dc:date>2000-08-25T12:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438932#M6491</link>
      <description>max_pe can range from 1 to 65535.</description>
      <pubDate>Fri, 25 Aug 2000 12:59:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438932#M6491</guid>
      <dc:creator>Cheryl Griffin</dc:creator>
      <dc:date>2000-08-25T12:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438933#M6492</link>
      <description>The max pe parameter is not for the volume group.  It is max physical extents per physical volume (disk).&lt;BR /&gt;When you create the volume group it will default "Max PE per PV" to the size of the largest disk you are adding at that time and it can not be changed later.  There have been several discussion related to this in the forums.&lt;BR /&gt;My preference is to increase it when I create a volume group.  If I'm starting with a 4GB drive I may set max pe to accomodate a 9GB drive in case I add that size drive in the future.&lt;BR /&gt;There is some overhead associated with increasing any of the parameters when you create a volume group.  There also is no formula or "right" answer to tell you whether to modify those parameters.  It depends on so many variable in your environment.&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Aug 2000 15:17:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438933#M6492</guid>
      <dc:creator>Dave Wherry</dc:creator>
      <dc:date>2000-08-25T15:17:14Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438934#M6493</link>
      <description>1) pvcreate -f /dev/rdsk/(c2t6d0) this in bracket is your disk hard ware path you can find your harddisk by doing ioscan.&lt;BR /&gt;2) vgextend /dev/vgxx/dev/dsk/c2t6d0&lt;BR /&gt;3)lvextend -L size of volgroup /dev/vgxx/lvxx&lt;BR /&gt;4)extendfs -F vxfs /dev/vgxx/rlvolxx&lt;BR /&gt;&lt;BR /&gt;after doing all this then mount your file system back again.&lt;BR /&gt;substitute xx with your vggroup and logical volumes.</description>
      <pubDate>Mon, 28 Aug 2000 13:13:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-problem/m-p/2438934#M6493</guid>
      <dc:creator>Cisco</dc:creator>
      <dc:date>2000-08-28T13:13:07Z</dc:date>
    </item>
  </channel>
</rss>

