From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l5TLdxdj026777 for ; Fri, 29 Jun 2007 17:39:59 -0400 Received: from drakesmith.net (drakesmith.net [64.62.223.80]) by mx1.redhat.com (8.13.1/8.13.1) with SMTP id l5TLduej030101 for ; Fri, 29 Jun 2007 17:39:56 -0400 Received: from PaulXP ([71.164.137.136]) by drakesmith.net for ; Fri, 29 Jun 2007 14:39:54 -0700 From: "WarlockD" References: <001201c7b9a3$4f0da2d0$ed28e870$@net> <46842D81.8090501@vdberg.org> <001601c7b9f6$8ff21990$afd64cb0$@net> <4684A547.8080302@vdberg.org> In-Reply-To: <4684A547.8080302@vdberg.org> Subject: RE: [linux-lvm] Serious problem and I don't know where to turn. Date: Fri, 29 Jun 2007 16:40:07 -0500 Message-ID: <004601c7ba96$10484160$30d8c420$@net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0047_01C7BA6C.27723960" Content-Language: en-us Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: 'LVM general discussion and development' This is a multipart message in MIME format. ------=_NextPart_000_0047_01C7BA6C.27723960 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=99t tell if it=E2=80=99s the iSCSI driver that = is doing it (The logical drive comes up as =E2=80=9Cbusy=E2=80=9D when I = try to access it after killing e2fsck) or something with lvm2 as = doubtful as that is. =20 I picked up some hard drives and put it in my old raid card for a RAID0, = and doing a dd if=3D/dev/ANIME/testlv of=3D/dev/sdc1. If this works, = and e2fsck works, then I got my data back, yea! =20 Now what to do with it:P =20 From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] = On Behalf Of Richard van den Berg Sent: Friday, June 29, 2007 1:23 AM To: LVM general discussion and development Subject: Re: [linux-lvm] Serious problem and I don't know where to turn. =20 WarlockD wrote: [root@server ~]# lvscan -a ACTIVE '/dev/VolGroup00/LogVol00' [147.00 GB] inherit ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit [root@server ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 Found volume group "ANIME" using metadata type lvm2 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: vgreduce --removemissing ANIME 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. Basicly, I have a volume called =E2=80=9CANIME-logical=E2=80=9D I am = trying to restore, but I don=E2=80=99t have the metadata. Is there a = way I can get to it? 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. 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. Sincerely, Richard van den Berg ------=_NextPart_000_0047_01C7BA6C.27723960 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

The good news is the = logical drive came up.=C2=A0 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.=C2=A0 I can=E2=80=99t tell if = it=E2=80=99s the iSCSI driver that is doing it (The logical drive comes up as =E2=80=9Cbusy=E2=80=9D when I = try to access it after killing e2fsck) or something with lvm2 as doubtful as that = is.

 

I picked up some hard = drives and put it in my old raid card for a RAID0, and doing a dd = if=3D/dev/ANIME/testlv of=3D/dev/sdc1.=C2=A0 If this works, and e2fsck works, then I got my = data back, yea!

 

Now what to do with = it:P

 

From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On Behalf Of Richard van = den Berg
Sent: Friday, June 29, 2007 1:23 AM
To: LVM general discussion and development
Subject: Re: [linux-lvm] Serious problem and I don't know where = to turn.

 

WarlockD wrote:

[root@server ~]# lvscan -a

  ACTIVE            '/dev/VolGroup00/LogVol00' [147.00 GB] inherit

  ACTIVE            '/dev/VolGroup00/LogVol01' [1.94 GB] inherit

[root@server ~]# vgscan

  Reading all physical volumes.  This = may take a while...

  Found volume group "VolGroup00" = using metadata type lvm2

  Found volume = group "ANIME" using metadata type lvm2


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:

vgreduce --removemissing ANIME

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.


Basicly, I have a = volume called =E2=80=9CANIME-logical=E2=80=9D I am trying to restore, but I = don=E2=80=99t have the metadata.  Is there a way I can get to it?


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.

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.

Sincerely,

Richard van den Berg

------=_NextPart_000_0047_01C7BA6C.27723960--