From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Pakulat <ap125@informatik.uni-rostock.de>
Subject: Re: [linux-lvm] Repair inconsistent PV
In-reply-to: <20030817012336.GA26462@debian.pakulat>
Message-id: <20030818214207.GC22587@debian.pakulat>
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
References: <20030816154556.GA23415@debian.pakulat>
 <20030817012336.GA26462@debian.pakulat>
Sender: linux-lvm-admin@sistina.com
Errors-To: linux-lvm-admin@sistina.com
Reply-To: linux-lvm@sistina.com
List-Help: <mailto:linux-lvm-request@sistina.com?subject=help>
List-Post: <mailto:linux-lvm@sistina.com>
List-Subscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=subscribe>
List-Unsubscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=unsubscribe>
List-Archive: <http://lists.sistina.com/pipermail/linux-lvm/>
Date: Mon Aug 18 16:43:01 2003
List-Id: <linux-lvm.redhat.com>
Content-Type: text/plain; charset="us-ascii"
To: linux-lvm@sistina.com

Hi,

only wanted to notify everyone, that I could now solve my problem with
hexedit and lvm.h. I changed the Major/Minor Numbers in both hdXX and
then looked at the VG Data, I found that the one in hdc2 seemed OK,
while the one in hda7 looked like random Data was written in it. So I
copied the VG Metadata into hda7 using dd. A vgscan marked lvtmp as
problematic, it was in hda7 but in the vgmetadata were only 3 LV's, so I
changed that and threw out the LV Metadata of that particular lv. It
is also the one I was deleting when the hardware error occured. Now I
can read my data again.

Andreas