<?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 vgextend for SG cluster lock disk in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898771#M633713</link>
    <description>When attempting to extend vg01 to include the future ServiceGuard cluster lock disk I get the following error message:&lt;BR /&gt;#vgextend /dev/vg01 /dev/dsk/c15t1d0&lt;BR /&gt;vgextend: Couldn't install the physical volume "/dev/dsk/c15t1d0".&lt;BR /&gt;No space left on device&lt;BR /&gt;&lt;BR /&gt;I preceeded this command with pvcreate /dev/rdsk/c15t1d0.&lt;BR /&gt;&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;BR /&gt;Stuart</description>
    <pubDate>Thu, 06 Feb 2003 18:47:25 GMT</pubDate>
    <dc:creator>Stuart Powell</dc:creator>
    <dc:date>2003-02-06T18:47:25Z</dc:date>
    <item>
      <title>vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898771#M633713</link>
      <description>When attempting to extend vg01 to include the future ServiceGuard cluster lock disk I get the following error message:&lt;BR /&gt;#vgextend /dev/vg01 /dev/dsk/c15t1d0&lt;BR /&gt;vgextend: Couldn't install the physical volume "/dev/dsk/c15t1d0".&lt;BR /&gt;No space left on device&lt;BR /&gt;&lt;BR /&gt;I preceeded this command with pvcreate /dev/rdsk/c15t1d0.&lt;BR /&gt;&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;BR /&gt;Stuart</description>
      <pubDate>Thu, 06 Feb 2003 18:47:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898771#M633713</guid>
      <dc:creator>Stuart Powell</dc:creator>
      <dc:date>2003-02-06T18:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898772#M633714</link>
      <description>Does a 'pvdisplay' or 'diskinfo' show size on the disk?&lt;BR /&gt;&lt;BR /&gt;Also, does a 'strings /etc/lvmtab |greop c15t1d0' show anything?&lt;BR /&gt;&lt;BR /&gt;I always use 'pvcreate -f' (force) to make doubly sure. Have you tried that?&lt;BR /&gt;&lt;BR /&gt;Share and Enjoy! Ian</description>
      <pubDate>Thu, 06 Feb 2003 18:49:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898772#M633714</guid>
      <dc:creator>Ian Dennison_1</dc:creator>
      <dc:date>2003-02-06T18:49:52Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898773#M633715</link>
      <description>#diskinfo /dev/rdsk/c15t1d0&lt;BR /&gt;SCSI describe of /dev/rdsk/c15t1d0:&lt;BR /&gt;             vendor: DGC     &lt;BR /&gt;         product id: C4700WDR5       &lt;BR /&gt;               type: direct access&lt;BR /&gt;               size: 4096 Kbytes&lt;BR /&gt;   bytes per sector: 512&lt;BR /&gt;Then I took your advice:&lt;BR /&gt;#pvcreate -f /dev/rdsk/c15t1d0&lt;BR /&gt;Physical volume "/dev/rdsk/c15t1d0" has been successfully created.&lt;BR /&gt;#vgextend /dev/vg01 /dev/dsk/c15t1d0&lt;BR /&gt;Current path "/dev/dsk/c13t1d1" is an alternate link, skip.&lt;BR /&gt;Current path "/dev/dsk/c15t1d1" is an alternate link, skip.&lt;BR /&gt;vgextend: Couldn't install the physical volume "/dev/dsk/c15t1d0".&lt;BR /&gt;No space left on device&lt;BR /&gt;&lt;BR /&gt;Stuart</description>
      <pubDate>Thu, 06 Feb 2003 18:52:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898773#M633715</guid>
      <dc:creator>Stuart Powell</dc:creator>
      <dc:date>2003-02-06T18:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898774#M633716</link>
      <description>How much is max_pe is set while creating vg01??&lt;BR /&gt;&lt;BR /&gt;If you are already reached the limit then you can not extend your vg01 any more.&lt;BR /&gt;&lt;BR /&gt;You have to set this limit while creating VG. Try recreating new VG &lt;BR /&gt;&lt;BR /&gt;-USA..</description>
      <pubDate>Thu, 06 Feb 2003 18:58:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898774#M633716</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2003-02-06T18:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898775#M633717</link>
      <description>Hi Stuart,&lt;BR /&gt;&lt;BR /&gt;Do a bdf and see if any of the file systems is at 100%. Particularly /. Look at your /var/adm/syslog/syslog.log for more messages with "no space".&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Thu, 06 Feb 2003 19:03:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898775#M633717</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2003-02-06T19:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898776#M633718</link>
      <description>USA - Max PE per PV is 62500 (I've run into that problem before, so I create this one big) Max PV is 16, and Cur PV is 2.&lt;BR /&gt;&lt;BR /&gt;Sir - Nothing is at 100% on any filesystem.  However the database space on vg02 is all used up.&lt;BR /&gt;&lt;BR /&gt;I'm leaving for the day, but would appreciate any other input.&lt;BR /&gt;&lt;BR /&gt;Stuart</description>
      <pubDate>Thu, 06 Feb 2003 19:15:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898776#M633718</guid>
      <dc:creator>Stuart Powell</dc:creator>
      <dc:date>2003-02-06T19:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898777#M633719</link>
      <description>Hi Stuart:&lt;BR /&gt;&lt;BR /&gt;I'm wondering, if you are running out of space in the root directory for the 'lvmconf' file, especially since your LVM data is going to be very large.&lt;BR /&gt;&lt;BR /&gt;Try the 'vgextend' *without* concommitant creation of the '/etc/lvmconf/vg01.conf' file:&lt;BR /&gt;&lt;BR /&gt;# vgextend -A n /dev/vg01 /dev/dsk/c15t1d0&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 06 Feb 2003 19:24:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898777#M633719</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2003-02-06T19:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898778#M633720</link>
      <description>Have you checked your syslog?&lt;BR /&gt;There may be a kernel parameter issue.  Perhaps you are running out of the inodes?  Check this with 'bdf -i'</description>
      <pubDate>Thu, 06 Feb 2003 22:12:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898778#M633720</guid>
      <dc:creator>Mladen Despic</dc:creator>
      <dc:date>2003-02-06T22:12:07Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898779#M633721</link>
      <description>Is disk o.k.? Try creatiing new VG using that disk.&lt;BR /&gt;&lt;BR /&gt;Paresh</description>
      <pubDate>Fri, 07 Feb 2003 11:30:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898779#M633721</guid>
      <dc:creator>Pradeep_3</dc:creator>
      <dc:date>2003-02-07T11:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898780#M633722</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;are the current recommended LVM, SCSI, FS patches installed? Is there no full filesystem (maybe a full root filesystem can cause such a message)? Is the volume group active on the node you try to extend it? Is the minor number unique? Is there a alternative path to the disk you are using instead of the primary one? ...?&lt;BR /&gt;&lt;BR /&gt;Please answer all this questions, hope that helps to fix the problem.&lt;BR /&gt;&lt;BR /&gt;Regards ...&lt;BR /&gt;Armin</description>
      <pubDate>Fri, 07 Feb 2003 11:44:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898780#M633722</guid>
      <dc:creator>Armin Feller</dc:creator>
      <dc:date>2003-02-07T11:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: vgextend for SG cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898781#M633723</link>
      <description>Thanks to everyone for your input.  I gave up and called HP's Response Center.  We got to the second line before the engineer asked the critical questions:  How big is the LUN? What is the PE size for the VG?  The answer to the first question was 4Mb and the answer to the second was 8Mb.  A physical device needs to be at least 1 PE.  I've got to recreate my cluster lock LUN's to be 8Mb.&lt;BR /&gt;&lt;BR /&gt;Stuart</description>
      <pubDate>Fri, 07 Feb 2003 18:02:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgextend-for-sg-cluster-lock-disk/m-p/2898781#M633723</guid>
      <dc:creator>Stuart Powell</dc:creator>
      <dc:date>2003-02-07T18:02:56Z</dc:date>
    </item>
  </channel>
</rss>

