From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <3B5A5DDC.60301@texas.net> Date: Sun, 22 Jul 2001 00:00:12 -0500 From: Ben Konosky MIME-Version: 1.0 Subject: Re: [linux-lvm] Help. References: <3B5A585F.1070003@texas.net> <424370000.995776829@dizzy> Content-Transfer-Encoding: 7bit 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: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-lvm@sistina.com vgexport -a gives no volume groups found. vgexport myvg gives volume group "myvg" doesn't exist. And yes, I had one LV spanning across all three PVs. Steven Lembark wrote: >- Ben Konosky on 07/21/01 23:36:47 -0500: > >>I had a VG that had three PVs in it, one of the PVs failed, is there any >>way to trick the VG into thinking it only has two PVs in it so I can >>*try* to mount it and see what data I can pull off the remainder. The >>file system is reiserfs, and it was the third PV in the group that died. >> > >vgexport and import it back with the valid PV's. You'll loose whatever >was on the missing PV. If any of the LV's spanned PV's then you'll loose >those LV's. > >sl >_______________________________________________ >linux-lvm mailing list >linux-lvm@sistina.com >http://lists.sistina.com/mailman/listinfo/linux-lvm >read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html > >