<?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: Removing inactivated volume groups in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560851#M646845</link>
    <description>Wrong place for question. Send this one to HPUX, System Administration. Betcha' have an answer within the hour.</description>
    <pubDate>Thu, 02 Aug 2001 17:10:01 GMT</pubDate>
    <dc:creator>paul courry</dc:creator>
    <dc:date>2001-08-02T17:10:01Z</dc:date>
    <item>
      <title>Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560850#M646844</link>
      <description>Successfully got my HP9000/L2000 onto a fabric SAN and got disks configured thru the LVM, running HPUX 11.0.  Then, the IS group switched my SAN cabling thru a different SAN director.  From that point on, my LVOLS were no longer accessible.  I assume because the paths changed.  HPUX found the same disks, but since they were on different paths than before, I could no longer get to them thru their old volume group, lvols, disk device names, etc.  I wound up creating a new volume group, lvols, etc. - essentially starting from scratch.  Luckily I had no critical data on the lvols, so no harm done.  But now I'm stuck with old volume group definitions that I cannot remove via SAM or command (vgremove, lvremove, etc.).  It complains that the vol group is not activated.  Well you can't activate a vol group if the path to the end device is no longer valid and the disks are not there.  Any idea how to clean up these old volume groups that are no longer needed/valid?&lt;BR /&gt;&lt;BR /&gt;thanks - I'm a bit of a rookie at this.</description>
      <pubDate>Thu, 02 Aug 2001 17:06:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560850#M646844</guid>
      <dc:creator>James Simmons</dc:creator>
      <dc:date>2001-08-02T17:06:37Z</dc:date>
    </item>
    <item>
      <title>Re: Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560851#M646845</link>
      <description>Wrong place for question. Send this one to HPUX, System Administration. Betcha' have an answer within the hour.</description>
      <pubDate>Thu, 02 Aug 2001 17:10:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560851#M646845</guid>
      <dc:creator>paul courry</dc:creator>
      <dc:date>2001-08-02T17:10:01Z</dc:date>
    </item>
    <item>
      <title>Re: Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560852#M646846</link>
      <description>thanks... you are correct.  should have posted this there instead.  I did that and got a quick response.  problem solved !</description>
      <pubDate>Thu, 02 Aug 2001 18:21:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560852#M646846</guid>
      <dc:creator>James Simmons</dc:creator>
      <dc:date>2001-08-02T18:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560853#M646847</link>
      <description>Get you old /etc/lvmtab file. Do strings on /etc/lvmtab and print it out.  This file give you relation ship b/w volume group and physical volume.&lt;BR /&gt;Get configuration files for missing directories from /etc/lvmconf directory. Configuration file names are like &lt;VOLUMGROUP name=""&gt;.conf&lt;BR /&gt;Now you have to know changes in PV names.  &lt;BR /&gt;Find which old PV name is changed to which new PV Name.&lt;BR /&gt;&lt;BR /&gt;Apply vgcfgrestore -f &lt;OLD volume="" group="" configuration="" file=""&gt; -o &lt;OLD pv="" name=""&gt; &amp;lt; new PV name&amp;gt; for every PV in that volume group&lt;BR /&gt;Apply vgimport &lt;OLD volume="" group="" name=""&gt; &lt;NEW pv="" name=""&gt; for PV in that volume group&lt;BR /&gt;Do vgchange -a y &amp;lt; old volume group name&amp;gt;&lt;BR /&gt;&lt;BR /&gt;This way you can restore volume groups that has pv names changed.&lt;BR /&gt;&lt;BR /&gt;Srini&lt;/NEW&gt;&lt;/OLD&gt;&lt;/OLD&gt;&lt;/OLD&gt;&lt;/VOLUMGROUP&gt;</description>
      <pubDate>Thu, 02 Aug 2001 18:59:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560853#M646847</guid>
      <dc:creator>Steve Tasker</dc:creator>
      <dc:date>2001-08-02T18:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560854#M646848</link>
      <description>Just vgexport the unwanted vg's, if you are not sure, do:&lt;BR /&gt;man vgexport&lt;BR /&gt;&lt;BR /&gt;And I have moved this to the correct forum :-}&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Aug 2001 06:15:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560854#M646848</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-08-03T06:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560855#M646849</link>
      <description>&amp;gt; I assume because the paths changed&lt;BR /&gt;This is exactly why.  The HW Path changed and therefore the device files changed.&lt;BR /&gt;&lt;BR /&gt;vgexport which is normally the method to do before changing the hardware will do the trick.. put it back the way it was, vgexport all vgs that'll change, then change h/w and vgimport the vg back in.&lt;BR /&gt;&lt;BR /&gt;Now at the moment, if you mv /etc/lvmtab /etc/lvmtab.donotdelete&lt;BR /&gt;and then issue a vgscan you will be able to recreate your lvm configuration and scan in the configuration of the lost/changed vg... without loosing data.&lt;BR /&gt;&lt;BR /&gt;BUT, vgscan will sort things in numerical order based on the device file, and your lvmtab may need some reworking after vgscan recreates it... vgreduce/vgextend.. this is only valid if you have alternate links and had them configured according to a particular failover design.&lt;BR /&gt;&lt;BR /&gt;In eithercase, read the manuals first and take care in reading on screen prompts.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Fri, 03 Aug 2001 06:22:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560855#M646849</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-08-03T06:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: Removing inactivated volume groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560856#M646850</link>
      <description>Thanks to all for the comments. vgexport quickly removed the old volume groups. Apologies for not doing my homework before posting.  I just didn't intuitively link vgexport with "removing" volume groups.  In my mind that should be a function of "vgremove", NO?  Usability flaw IMHO.</description>
      <pubDate>Fri, 03 Aug 2001 13:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/removing-inactivated-volume-groups/m-p/2560856#M646850</guid>
      <dc:creator>James Simmons</dc:creator>
      <dc:date>2001-08-03T13:34:29Z</dc:date>
    </item>
  </channel>
</rss>

