From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1032446901.3d89e3b5b98de@lola.Pin.LU> From: Christian Limpach Subject: Re: [linux-lvm] Removing an old disk, and some vgexport/import love.. References: <002001c25fa7$482b2740$ccc67140@ownage> <20020919115935.A32578@sistina.com> <000d01c2615f$7f7d7130$ddc67140@nolove> In-Reply-To: <000d01c2615f$7f7d7130$ddc67140@nolove> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Thu Sep 19 09:50:39 2002 List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-lvm@sistina.com, Matt Quoting Matt : > > > PV Name (#) /dev/hde1 (1) > > > PV Name (#) /dev/hdg1 (3) > > > PV Name (#) /dev/hdf1 (4) what happened here is that vgreduce doesn't renumber the PVs and if you export the VG and try to reimport it, vgimport complains because it expects the PVs to be numbered contiguously. I had this same problem a couple of weeks ago. I solved it by patching the VGDA on the new disk, renumbering the PV to get the number of the PV I had removed and then everything was ok again. It seems like you'll need to renumber /dev/hdf1 to be PV#2 from being PV#4. Check with pvdata that the PVs are indeed numbered as above, make a copy of the first few sectors of /dev/hdf1 and then try the following: printf "\0002" | dd of=/dev/hdf1 bs=1 count=1 seek=432 conv=notrunc -- Christian Limpach