HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Missing lvol after crash
Operating System - Linux
1828370
Members
3174
Online
109976
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2006 01:50 AM
08-31-2006 01:50 AM
Hi,
After expirencing a crash on a linux Red-Hat 4 As system, one of the lvols has vanished...
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".
I would like to know if I can recrate the lvols table acording the dm files ? or there is another solution to the problem ?
Thanks.
After expirencing a crash on a linux Red-Hat 4 As system, one of the lvols has vanished...
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".
I would like to know if I can recrate the lvols table acording the dm files ? or there is another solution to the problem ?
Thanks.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2006 06:38 AM
08-31-2006 06:38 AM
Solution
Interesting... I would take a look at the PV(s) and see what shows up;
1. use vgdisplay -v and get the PV name(s)
2. use 'dd' to write out the header on the disk(s);
dd if=/dev/cciss/c0d0p2 of=/tmp/dd.out count=1 bs=64k
Look for the "logical_volumes" section in /tmp/dd.out. Just verify the LV info is still there for the missing LV.
If it is there then perhaps if you 'vgexport' then 'vgimport' the volume group you can recover it.
David
1. use vgdisplay -v
2. use 'dd' to write out the header on the disk(s);
dd if=/dev/cciss/c0d0p2 of=/tmp/dd.out count=1 bs=64k
Look for the "logical_volumes" section in /tmp/dd.out. Just verify the LV info is still there for the missing LV.
If it is there then perhaps if you 'vgexport' then 'vgimport' the volume group you can recover it.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2006 06:59 PM
09-02-2006 06:59 PM
Re: Missing lvol after crash
Thanks for the reply....
The problem is that in the system startup the corupted lvol is lvol11 that belongs to vg01 but its file is apsolutly missing....
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.
To simplify the problem, all the minor numbers are there, but the connection between the dm files and the lvols is some how broken....
Thanks ahead....
The problem is that in the system startup the corupted lvol is lvol11 that belongs to vg01 but its file is apsolutly missing....
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.
To simplify the problem, all the minor numbers are there, but the connection between the dm files and the lvols is some how broken....
Thanks ahead....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2006 04:43 AM
09-06-2006 04:43 AM
Re: Missing lvol after crash
Sorry for the late reply.
Okay, I think I understand the problem, but let me make sure;
1. After the crash you no longer see /dev/vg01/lvol11
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
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.
Could you post;
1. ls -l /dev/vg01
2. ls -l /dev/mapper/vg01-*
3. ls -l /dev/dm-*
4. vgdisplay -v vg01
This info will help troubleshoot the problem.
Thanks,
David
Okay, I think I understand the problem, but let me make sure;
1. After the crash you no longer see /dev/vg01/lvol11
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
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.
Could you post;
1. ls -l /dev/vg01
2. ls -l /dev/mapper/vg01-*
3. ls -l /dev/dm-*
4. vgdisplay -v vg01
This info will help troubleshoot the problem.
Thanks,
David
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP