<?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 vg issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537019#M222458</link>
    <description>We had to create a vg for a couple of new directories for an Oracle migration.  This caused problems with the /dev/vg### in not allowing us to remove the created vg's which once created in conflict would not show up under the file systems and disk in SAM.  I was able to fix this problem, by manually going into the /dev directory and dropping all of the vg(s) I created in SAM.  But after a reboot in this process, one of the vg(s) which we do use was dismounted and deactivated from SAM.  I checked the /etc/fstab and the vg(s) which I commented out are disabled, but also one I did not is also disabled in SAM.&lt;BR /&gt;What I need to know is how do I get SAM to re-activate the vg in question?</description>
    <pubDate>Tue, 03 May 2005 17:03:49 GMT</pubDate>
    <dc:creator>raymond cavanaugh_2</dc:creator>
    <dc:date>2005-05-03T17:03:49Z</dc:date>
    <item>
      <title>vg issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537019#M222458</link>
      <description>We had to create a vg for a couple of new directories for an Oracle migration.  This caused problems with the /dev/vg### in not allowing us to remove the created vg's which once created in conflict would not show up under the file systems and disk in SAM.  I was able to fix this problem, by manually going into the /dev directory and dropping all of the vg(s) I created in SAM.  But after a reboot in this process, one of the vg(s) which we do use was dismounted and deactivated from SAM.  I checked the /etc/fstab and the vg(s) which I commented out are disabled, but also one I did not is also disabled in SAM.&lt;BR /&gt;What I need to know is how do I get SAM to re-activate the vg in question?</description>
      <pubDate>Tue, 03 May 2005 17:03:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537019#M222458</guid>
      <dc:creator>raymond cavanaugh_2</dc:creator>
      <dc:date>2005-05-03T17:03:49Z</dc:date>
    </item>
    <item>
      <title>Re: vg issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537020#M222459</link>
      <description>You didn't quite do the required steps. Your /etc/lvmtab still has entries in it. You need to do a vgexport /dev/vgxx. This will remove the /dev/vgxx/* entries and, in addition, remove the corresponding entries in /etc/lvmtab. Do a "strings /etc/lvmtab" and see if your VG is still in lvmtab. The good news is that vgexport will still work eventhough you have manually removed the device nodes and directory under /dev.</description>
      <pubDate>Tue, 03 May 2005 17:23:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537020#M222459</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-05-03T17:23:58Z</dc:date>
    </item>
    <item>
      <title>Re: vg issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537021#M222460</link>
      <description>vgimport will bring the vg configuration information back in and allow you to activate the volume group as follows:&lt;BR /&gt;&lt;BR /&gt;vgchange -a y vg##&lt;BR /&gt;&lt;BR /&gt;To make a volume group go away the command is vgexport.&lt;BR /&gt;&lt;BR /&gt;Prior to doing this if its to go away forever use lvremove to remove all of the logcial volumes.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 03 May 2005 17:30:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537021#M222460</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-05-03T17:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: vg issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537022#M222461</link>
      <description>You are wrongs in removing vg&lt;BR /&gt;If you want to remove let use&lt;BR /&gt;#lvremove lvname - all lv on vg&lt;BR /&gt;#vgremove vgname pvname&lt;BR /&gt;OR &lt;BR /&gt;#vgexport vgname.&lt;BR /&gt;DO NOT REMOVE FOLDER ONLY. VG INFOR STILL KEEP IN /ETC/FSTAB.</description>
      <pubDate>Tue, 03 May 2005 20:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537022#M222461</guid>
      <dc:creator>Nguyen Anh Tien</dc:creator>
      <dc:date>2005-05-03T20:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: vg issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537023#M222462</link>
      <description>You need to "export" the vgs from the /etc/lvmtab file using vgexport.  Use vgimport to put the vg back into the lvmtab file.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Isralyn</description>
      <pubDate>Wed, 04 May 2005 01:38:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vg-issue/m-p/3537023#M222462</guid>
      <dc:creator>Isralyn Manalac_1</dc:creator>
      <dc:date>2005-05-04T01:38:19Z</dc:date>
    </item>
  </channel>
</rss>

