<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>The good news is the logical
drive came up. I just recreated the logical drive exactly as it was and its
even detected, with a missing superblock, as an ext3 partition. The bad news is
that e2fsck still froze on me. I can’t tell if it’s the iSCSI driver that is
doing it (The logical drive comes up as “busy” when I try to access it after
killing e2fsck) or something with lvm2 as doubtful as that is.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I picked up some hard drives and
put it in my old raid card for a RAID0, and doing a dd if=/dev/ANIME/testlv
of=/dev/sdc1. If this works, and e2fsck works, then I got my data back, yea!<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Now what to do with it:P<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> linux-lvm-bounces@redhat.com
[mailto:linux-lvm-bounces@redhat.com] <b>On Behalf Of </b>Richard van den Berg<br>
<b>Sent:</b> Friday, June 29, 2007 1:23 AM<br>
<b>To:</b> LVM general discussion and development<br>
<b>Subject:</b> Re: [linux-lvm] Serious problem and I don't know where to turn.<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>WarlockD wrote:<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>[root@server ~]# lvscan -a</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>
ACTIVE
'/dev/VolGroup00/LogVol00' [147.00 GB] inherit</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>
ACTIVE
'/dev/VolGroup00/LogVol01' [1.94 GB] inherit</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>[root@server ~]# vgscan</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> Reading all physical volumes. This may take
a while...</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> Found volume group "VolGroup00" using
metadata type lvm2</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> Found volume group
"ANIME" using metadata type lvm2</span><o:p></o:p></p>
<p class=MsoNormal><br>
So the vg "ANIME" is found, but is not activated? That kind of makes
sense because it is missing the pv on the deleted /dev/sdb2 partition.
According to the vgreduce man pages you can:<br>
<br>
vgreduce --removemissing ANIME<br>
<br>
to remove all missing physical volumes from the volume group and make the
volume group consistent again. It's a good idea to run this option with
--test first to find out what it would remove before running it for real.
There is also "--partial" option you can use to activate vgs and lvs
even if they are missing data. Read the man pages and be very careful before
you proceed.<br>
<br>
<br>
<o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Basicly, I have a volume called
“ANIME-logical” I am trying to restore, but I don’t have the metadata. Is
there a way I can get to it?</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>
Without the metadata that's going to be tough. If the filesystem is all
continuous on your RAID5 partition, technically you should be able to mount it
if you can create a device pointing at the right start, and with the right
size. Good luck figuring that out.<br>
<br>
Another approach could be to recreate the /dev/sdb2 partition in exactly the
same way you did before. The metadata might still be there, and the vg might
come up.<br>
<br>
Sincerely,<br>
<br>
Richard van den Berg<o:p></o:p></span></p>
</div>
</body>
</html>