<?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: Missing lvol after crash in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854342#M24959</link>
    <description>Thanks for the reply....&lt;BR /&gt;The problem is that in the system startup the corupted lvol is lvol11 that belongs to vg01 but its file is apsolutly missing....&lt;BR /&gt;But if you check the dm files the corupted dm is dm-8 that refers to vg00 and its imposible to do a vgexport to the system vg.&lt;BR /&gt;To simplify the problem, all the minor numbers are there, but the connection between the dm files and the lvols is some how broken....&lt;BR /&gt;Thanks ahead.... &lt;BR /&gt;</description>
    <pubDate>Sun, 03 Sep 2006 01:59:20 GMT</pubDate>
    <dc:creator>Eli_pok</dc:creator>
    <dc:date>2006-09-03T01:59:20Z</dc:date>
    <item>
      <title>Missing lvol after crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854340#M24957</link>
      <description>Hi,&lt;BR /&gt;After expirencing a crash on a linux Red-Hat 4 As system, one of the lvols has vanished...&lt;BR /&gt;The problem is that the /dev/dm files are all there, exept one that was corupted and a new fs was created on it. Unfortuntly, the problem still ocurs on startup saying lvol11 is missing. Another problem that happened after crash was a message about an "open file descriptor".&lt;BR /&gt;I would like to know if I can recrate the lvols table acording the dm files ? or there is another solution to the problem ?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 31 Aug 2006 08:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854340#M24957</guid>
      <dc:creator>Eli_pok</dc:creator>
      <dc:date>2006-08-31T08:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Missing lvol after crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854341#M24958</link>
      <description>Interesting... I would take a look at the PV(s) and see what shows up;&lt;BR /&gt;&lt;BR /&gt;1. use vgdisplay -v &lt;VG&gt; and get the PV name(s)&lt;BR /&gt;2. use 'dd' to write out the header on the disk(s);&lt;BR /&gt;&lt;BR /&gt;dd if=/dev/cciss/c0d0p2 of=/tmp/dd.out count=1 bs=64k&lt;BR /&gt;&lt;BR /&gt;Look for the "logical_volumes" section in /tmp/dd.out. Just verify the LV info is still there for the missing LV.&lt;BR /&gt;&lt;BR /&gt;If it is there then perhaps if you 'vgexport' then 'vgimport' the volume group you can recover it.&lt;BR /&gt;&lt;BR /&gt;David&lt;/VG&gt;</description>
      <pubDate>Thu, 31 Aug 2006 13:38:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854341#M24958</guid>
      <dc:creator>David Child_1</dc:creator>
      <dc:date>2006-08-31T13:38:10Z</dc:date>
    </item>
    <item>
      <title>Re: Missing lvol after crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854342#M24959</link>
      <description>Thanks for the reply....&lt;BR /&gt;The problem is that in the system startup the corupted lvol is lvol11 that belongs to vg01 but its file is apsolutly missing....&lt;BR /&gt;But if you check the dm files the corupted dm is dm-8 that refers to vg00 and its imposible to do a vgexport to the system vg.&lt;BR /&gt;To simplify the problem, all the minor numbers are there, but the connection between the dm files and the lvols is some how broken....&lt;BR /&gt;Thanks ahead.... &lt;BR /&gt;</description>
      <pubDate>Sun, 03 Sep 2006 01:59:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854342#M24959</guid>
      <dc:creator>Eli_pok</dc:creator>
      <dc:date>2006-09-03T01:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: Missing lvol after crash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854343#M24960</link>
      <description>Sorry for the late reply. &lt;BR /&gt;&lt;BR /&gt;Okay, I think I understand the problem, but let me make sure;&lt;BR /&gt;&lt;BR /&gt;1. After the crash you no longer see /dev/vg01/lvol11&lt;BR /&gt;&lt;BR /&gt;2. The /dev/dm-8 device for this logical volume is on the box, but it points to one of the logical volumes in vg00&lt;BR /&gt;&lt;BR /&gt;Every time your Linux server reboots it will re-create all the devices in /dev. There is no guarantee that dm-8 = /dev/vg01/lvol11.&lt;BR /&gt;&lt;BR /&gt;Could you post;&lt;BR /&gt;&lt;BR /&gt;1. ls -l /dev/vg01&lt;BR /&gt;2. ls -l /dev/mapper/vg01-*&lt;BR /&gt;3. ls -l /dev/dm-*&lt;BR /&gt;4. vgdisplay -v vg01&lt;BR /&gt;&lt;BR /&gt;This info will help troubleshoot the problem.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;David</description>
      <pubDate>Wed, 06 Sep 2006 11:43:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/missing-lvol-after-crash/m-p/3854343#M24960</guid>
      <dc:creator>David Child_1</dc:creator>
      <dc:date>2006-09-06T11:43:04Z</dc:date>
    </item>
  </channel>
</rss>

