<?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 vgdisplay - invalid lv in extent map in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969142#M46941</link>
    <description>We just recently rebuilt a RH ES3 to RH 4.&lt;BR /&gt;Everything is working fine, database is working on these LV's, things are getting written too, except for vgdisplay.&lt;BR /&gt;&lt;BR /&gt;Now everything is under /dev/mapper instead of /dev/vg01&lt;BR /&gt;But, from further reading this should not be an issue.&lt;BR /&gt;&lt;BR /&gt;I believe this is also causing an issue when we try to create a lv for snap shot backup.&lt;BR /&gt;&lt;BR /&gt;Error:&lt;BR /&gt;[root@server ~]# vgdisplay&lt;BR /&gt;  invalid lv in extent map&lt;BR /&gt;  Couldn't fill logical volume maps.&lt;BR /&gt;  invalid lv in extent map&lt;BR /&gt;  Couldn't fill logical volume maps.&lt;BR /&gt;  Volume group "vg01" doesn't exist&lt;BR /&gt;  --- Volume group ---&lt;BR /&gt;  VG Name               vg00&lt;BR /&gt;  System ID&lt;BR /&gt;  Format                lvm2&lt;BR /&gt;  Metadata Areas        1&lt;BR /&gt;  Metadata Sequence No  8&lt;BR /&gt;  VG Access             read/write&lt;BR /&gt;  VG Status             resizable&lt;BR /&gt;  MAX LV                0&lt;BR /&gt;  Cur LV                6&lt;BR /&gt;  Open LV               6&lt;BR /&gt;  Max PV                0&lt;BR /&gt;  Cur PV                1&lt;BR /&gt;  Act PV                1&lt;BR /&gt;  VG Size               33.77 GB&lt;BR /&gt;  PE Size               4.00 MB&lt;BR /&gt;  Total PE              8644&lt;BR /&gt;  Alloc PE / Size       5888 / 23.00 GB&lt;BR /&gt;  Free  PE / Size       2756 / 10.77 GB&lt;BR /&gt;  VG UUID               knNrX5-yWNG-PxYh-Ra9c-VBaQ-5NYn-Dt3UoI&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Error on Backup:&lt;BR /&gt;$LVCREATE --size 1000M --snapshot -n backup1 /dev/vg01/lvdb1&lt;BR /&gt;&lt;BR /&gt; invalid lv in extent map&lt;BR /&gt;  Couldn't fill logical volume maps.&lt;BR /&gt;  invalid lv in extent map&lt;BR /&gt;  Volume group for uuid not found: QjeRKVX0rmt9Pb1adWv8jXuP8LfwwsUE0000000000000000000000000&lt;BR /&gt;0000002&lt;BR /&gt;  Failed to suspend origin lvdb1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[root@server ~]# df -h&lt;BR /&gt;Filesystem            Size  Used Avail Use% Mounted on&lt;BR /&gt;/dev/mapper/vg00-root&lt;BR /&gt;                     1008M  143M  814M  15% /&lt;BR /&gt;/dev/sda2              99M   13M   82M  14% /boot&lt;BR /&gt;/dev/mapper/vg01-lvappbk&lt;BR /&gt;                       20G  3.4G   16G  18% /dbck&lt;BR /&gt;none                  2.0G     0  2.0G   0% /dev/shm&lt;BR /&gt;/dev/mapper/vg01-lvhome&lt;BR /&gt;                      5.0G  3.1G  1.7G  66% /home&lt;BR /&gt;/dev/mapper/vg00-opt  4.0G   66M  3.7G   2% /opt&lt;BR /&gt;/dev/mapper/vg01-lvoracle&lt;BR /&gt;                      4.0G  2.0G  1.8G  53% /opt/app/oracle&lt;BR /&gt;/dev/mapper/vg01-lvarchlog&lt;BR /&gt;                      3.0G   33M  2.8G   2% /opt/app/oracle/archivelog/acdb&lt;BR /&gt;/dev/mapper/vg01-lvdbbk&lt;BR /&gt;                       30G   33M   28G   1% /opt/app/oracle/backup&lt;BR /&gt;/dev/mapper/vg01-lvdb1&lt;BR /&gt;                      9.9G  7.3G  2.1G  78% /opt/app/oracle/oradata/db1&lt;BR /&gt;/dev/mapper/vg01-lvdb2&lt;BR /&gt;                      9.9G  2.9G  6.6G  31% /opt/app/oracle/oradata/db2&lt;BR /&gt;/dev/mapper/vg01-lvdb3&lt;BR /&gt;                      9.9G  4.6G  4.8G  49% /opt/app/oracle/oradata/db3&lt;BR /&gt;/dev/mapper/vg01-lvmob&lt;BR /&gt;                       15G   14G  306M  98% /opt/app/oracle/oradata/mol&lt;BR /&gt;/dev/mapper/vg01-lvsstrs&lt;BR /&gt;                      5.0G  2.8G  2.0G  59% /opt/app/oracle/oradata/ssst&lt;BR /&gt;/dev/mapper/vg01-lvwfrpt&lt;BR /&gt;                      5.0G  1.1G  3.7G  22% /opt/app/oracle/oradata/wfrt&lt;BR /&gt;/dev/mapper/vg00-tmp  2.0G   36M  1.9G   2% /tmp&lt;BR /&gt;/dev/mapper/vg00-usr  9.9G  699M  8.7G   8% /usr&lt;BR /&gt;/dev/mapper/vg00-var  2.0G   65M  1.9G   4% /var&lt;BR /&gt;</description>
    <pubDate>Wed, 22 Mar 2006 14:39:36 GMT</pubDate>
    <dc:creator>Ratzie</dc:creator>
    <dc:date>2006-03-22T14:39:36Z</dc:date>
    <item>
      <title>vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969142#M46941</link>
      <description>We just recently rebuilt a RH ES3 to RH 4.&lt;BR /&gt;Everything is working fine, database is working on these LV's, things are getting written too, except for vgdisplay.&lt;BR /&gt;&lt;BR /&gt;Now everything is under /dev/mapper instead of /dev/vg01&lt;BR /&gt;But, from further reading this should not be an issue.&lt;BR /&gt;&lt;BR /&gt;I believe this is also causing an issue when we try to create a lv for snap shot backup.&lt;BR /&gt;&lt;BR /&gt;Error:&lt;BR /&gt;[root@server ~]# vgdisplay&lt;BR /&gt;  invalid lv in extent map&lt;BR /&gt;  Couldn't fill logical volume maps.&lt;BR /&gt;  invalid lv in extent map&lt;BR /&gt;  Couldn't fill logical volume maps.&lt;BR /&gt;  Volume group "vg01" doesn't exist&lt;BR /&gt;  --- Volume group ---&lt;BR /&gt;  VG Name               vg00&lt;BR /&gt;  System ID&lt;BR /&gt;  Format                lvm2&lt;BR /&gt;  Metadata Areas        1&lt;BR /&gt;  Metadata Sequence No  8&lt;BR /&gt;  VG Access             read/write&lt;BR /&gt;  VG Status             resizable&lt;BR /&gt;  MAX LV                0&lt;BR /&gt;  Cur LV                6&lt;BR /&gt;  Open LV               6&lt;BR /&gt;  Max PV                0&lt;BR /&gt;  Cur PV                1&lt;BR /&gt;  Act PV                1&lt;BR /&gt;  VG Size               33.77 GB&lt;BR /&gt;  PE Size               4.00 MB&lt;BR /&gt;  Total PE              8644&lt;BR /&gt;  Alloc PE / Size       5888 / 23.00 GB&lt;BR /&gt;  Free  PE / Size       2756 / 10.77 GB&lt;BR /&gt;  VG UUID               knNrX5-yWNG-PxYh-Ra9c-VBaQ-5NYn-Dt3UoI&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Error on Backup:&lt;BR /&gt;$LVCREATE --size 1000M --snapshot -n backup1 /dev/vg01/lvdb1&lt;BR /&gt;&lt;BR /&gt; invalid lv in extent map&lt;BR /&gt;  Couldn't fill logical volume maps.&lt;BR /&gt;  invalid lv in extent map&lt;BR /&gt;  Volume group for uuid not found: QjeRKVX0rmt9Pb1adWv8jXuP8LfwwsUE0000000000000000000000000&lt;BR /&gt;0000002&lt;BR /&gt;  Failed to suspend origin lvdb1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[root@server ~]# df -h&lt;BR /&gt;Filesystem            Size  Used Avail Use% Mounted on&lt;BR /&gt;/dev/mapper/vg00-root&lt;BR /&gt;                     1008M  143M  814M  15% /&lt;BR /&gt;/dev/sda2              99M   13M   82M  14% /boot&lt;BR /&gt;/dev/mapper/vg01-lvappbk&lt;BR /&gt;                       20G  3.4G   16G  18% /dbck&lt;BR /&gt;none                  2.0G     0  2.0G   0% /dev/shm&lt;BR /&gt;/dev/mapper/vg01-lvhome&lt;BR /&gt;                      5.0G  3.1G  1.7G  66% /home&lt;BR /&gt;/dev/mapper/vg00-opt  4.0G   66M  3.7G   2% /opt&lt;BR /&gt;/dev/mapper/vg01-lvoracle&lt;BR /&gt;                      4.0G  2.0G  1.8G  53% /opt/app/oracle&lt;BR /&gt;/dev/mapper/vg01-lvarchlog&lt;BR /&gt;                      3.0G   33M  2.8G   2% /opt/app/oracle/archivelog/acdb&lt;BR /&gt;/dev/mapper/vg01-lvdbbk&lt;BR /&gt;                       30G   33M   28G   1% /opt/app/oracle/backup&lt;BR /&gt;/dev/mapper/vg01-lvdb1&lt;BR /&gt;                      9.9G  7.3G  2.1G  78% /opt/app/oracle/oradata/db1&lt;BR /&gt;/dev/mapper/vg01-lvdb2&lt;BR /&gt;                      9.9G  2.9G  6.6G  31% /opt/app/oracle/oradata/db2&lt;BR /&gt;/dev/mapper/vg01-lvdb3&lt;BR /&gt;                      9.9G  4.6G  4.8G  49% /opt/app/oracle/oradata/db3&lt;BR /&gt;/dev/mapper/vg01-lvmob&lt;BR /&gt;                       15G   14G  306M  98% /opt/app/oracle/oradata/mol&lt;BR /&gt;/dev/mapper/vg01-lvsstrs&lt;BR /&gt;                      5.0G  2.8G  2.0G  59% /opt/app/oracle/oradata/ssst&lt;BR /&gt;/dev/mapper/vg01-lvwfrpt&lt;BR /&gt;                      5.0G  1.1G  3.7G  22% /opt/app/oracle/oradata/wfrt&lt;BR /&gt;/dev/mapper/vg00-tmp  2.0G   36M  1.9G   2% /tmp&lt;BR /&gt;/dev/mapper/vg00-usr  9.9G  699M  8.7G   8% /usr&lt;BR /&gt;/dev/mapper/vg00-var  2.0G   65M  1.9G   4% /var&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Mar 2006 14:39:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969142#M46941</guid>
      <dc:creator>Ratzie</dc:creator>
      <dc:date>2006-03-22T14:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969143#M46942</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;How about:&lt;BR /&gt;&lt;BR /&gt;vgdisplay /dev/mapper/vg01&lt;BR /&gt;&lt;BR /&gt;or&lt;BR /&gt;&lt;BR /&gt;vgdisplay -v /dev/mapper/vg01&lt;BR /&gt;&lt;BR /&gt;I'm just feeling my way around with lvm on Linux but I'm thinking my command should work.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 22 Mar 2006 15:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969143#M46942</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-22T15:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969144#M46943</link>
      <description>All poop out.&lt;BR /&gt;&lt;BR /&gt;[root@server ~]# vgdisplay /dev/mapper/vg01&lt;BR /&gt;  Invalid volume group name: mapper/vg01&lt;BR /&gt;[root@server ~]# vgdisplay -v /dev/mapper/vg01&lt;BR /&gt;    Using volume group(s) on command line&lt;BR /&gt;  Invalid volume group name: mapper/vg01&lt;BR /&gt;[root@server ~]# vgdisplay /dev/mapper/vg01-lvdb1&lt;BR /&gt;  Invalid volume group name: mapper/vg01-lvdb1&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Mar 2006 15:17:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969144#M46943</guid>
      <dc:creator>Ratzie</dc:creator>
      <dc:date>2006-03-22T15:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969145#M46944</link>
      <description>Run vgcfgbackup -f /etc/lvm/backup/vg01-lvm.bak vg01&lt;BR /&gt;&lt;BR /&gt;Then run&lt;BR /&gt;&lt;BR /&gt;vgcfgrestore vg01&lt;BR /&gt;&lt;BR /&gt;To try to fix the LVM database configuration.</description>
      <pubDate>Wed, 22 Mar 2006 16:44:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969145#M46944</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-03-22T16:44:38Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969146#M46945</link>
      <description>Will this harm the data on the logical volume?&lt;BR /&gt;&lt;BR /&gt;Any precautions?</description>
      <pubDate>Wed, 22 Mar 2006 17:40:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969146#M46945</guid>
      <dc:creator>Ratzie</dc:creator>
      <dc:date>2006-03-22T17:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969147#M46946</link>
      <description>Always have a good backup before any changes related to disk. The command should not generate any problems, at maximum should fail.</description>
      <pubDate>Thu, 23 Mar 2006 07:45:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969147#M46946</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-03-23T07:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969148#M46947</link>
      <description>lvm on linux is more or less the same as on HP-UX.&lt;BR /&gt;&lt;BR /&gt;On HP-UX I would try vgscan -v.&lt;BR /&gt;Ypu may even need vgimport.&lt;BR /&gt;Check the man pages...&lt;BR /&gt;&lt;BR /&gt;JP</description>
      <pubDate>Tue, 28 Mar 2006 13:35:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969148#M46947</guid>
      <dc:creator>Jeroen Peereboom</dc:creator>
      <dc:date>2006-03-28T13:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: vgdisplay - invalid lv in extent map</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969149#M46948</link>
      <description>I can not run vgcfgbackup or any vg command. I have opened up a trouble with RedHat.</description>
      <pubDate>Tue, 28 Mar 2006 13:48:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgdisplay-invalid-lv-in-extent-map/m-p/4969149#M46948</guid>
      <dc:creator>Ratzie</dc:creator>
      <dc:date>2006-03-28T13:48:47Z</dc:date>
    </item>
  </channel>
</rss>

