<?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: invalid lv number in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927559#M634476</link>
    <description>Are there any other logical volumes in this VG?  If not, you could try running vgexport/vgimport.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
    <pubDate>Fri, 14 Mar 2003 14:32:36 GMT</pubDate>
    <dc:creator>Pete Randall</dc:creator>
    <dc:date>2003-03-14T14:32:36Z</dc:date>
    <item>
      <title>invalid lv number</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927558#M634475</link>
      <description>In a volume group a logical volume was created with 1.5 GB size. When removing the LV by mistake the raw logical volume was removed using rm command. Later on when trying to remove the logical volume it was giving a message "can't remove, invalid lv number". The lvol was removed using rm command. But it did now free the space. When lvdisplay command was tried it did'nt show the logical volume. &lt;BR /&gt;&lt;BR /&gt;Can anybody pls help in this matter.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Mar 2003 14:27:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927558#M634475</guid>
      <dc:creator>Amit Manna_6</dc:creator>
      <dc:date>2003-03-14T14:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: invalid lv number</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927559#M634476</link>
      <description>Are there any other logical volumes in this VG?  If not, you could try running vgexport/vgimport.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 14 Mar 2003 14:32:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927559#M634476</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2003-03-14T14:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: invalid lv number</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927560#M634477</link>
      <description>there are other logical volumes in this volume group.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Mar 2003 14:35:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927560#M634477</guid>
      <dc:creator>Amit Manna_6</dc:creator>
      <dc:date>2003-03-14T14:35:06Z</dc:date>
    </item>
    <item>
      <title>Re: invalid lv number</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927561#M634478</link>
      <description>Have you tried doing a vgcfgrestore for the volume group to get things back...and then remove the lvol properly?&lt;BR /&gt;&lt;BR /&gt;Just a thought,&lt;BR /&gt;Rita&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Mar 2003 14:40:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927561#M634478</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2003-03-14T14:40:08Z</dc:date>
    </item>
    <item>
      <title>Re: invalid lv number</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927562#M634479</link>
      <description>You can simply recreate the LV device files...&lt;BR /&gt;&lt;BR /&gt;cd /dev/vg??&lt;BR /&gt;&lt;BR /&gt;mknod rlvolx c 64 0xVV000?&lt;BR /&gt;mknod lvolx b 64 0xVV000?&lt;BR /&gt;&lt;BR /&gt;where VV is the VG number (same as the group file) and ? is the relevant LV number. If you don't know it, make an informed guess from numbers that you don't have already (check with ll).&lt;BR /&gt;&lt;BR /&gt;Then lvremove -f to remove the LV.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John</description>
      <pubDate>Fri, 14 Mar 2003 14:47:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927562#M634479</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2003-03-14T14:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: invalid lv number</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927563#M634480</link>
      <description>You DON'T need to do a vgcfgrestore as all the information on the disks is currently correct. All you've done is removed the device files. As I stated earlier, you can just create them without even deactivating the VG, something I've done many times (also renaming them).&lt;BR /&gt;&lt;BR /&gt;If you are uneasy about doing it then an alternative is to deactivate then export the VG (with a map), then reimport. Your 'rogue' LV will be the one not mentioned in your map. &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John</description>
      <pubDate>Fri, 14 Mar 2003 15:13:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/invalid-lv-number/m-p/2927563#M634480</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2003-03-14T15:13:09Z</dc:date>
    </item>
  </channel>
</rss>

