Ugh... # vgexport -av vgexport -- locking logical volume manager vgexport -- checking volume group name vgexport -- checking volume group activity vgexport -- reading data of volume group "rootvg" from disk(s) vgexport -- only found 0 of 39 LEs for LV /dev/rootvg/tmp (0) vgexport -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" reading data of volume group "rootvg" vgexport -- unlocking logical volume manager Other ideas? Thanks, Dan On Wed, 2003-01-08 at 14:21, Steven Lembark wrote: > -- Daniel Wittenberg <daniel-wittenberg@uiowa.edu> > > > I had 2 drives in my machine, with a VG across both of them. The only > > thing on the second drive was part of /tmp, so when the second drive > > died I didn't really lose anything. But I have problems now because I > > can't activate the VG because part of it is missing, but I can't remove > > tmp, so it's a catch-22. Is there anyway to remove an LV without > > activating the VG? Or another way I can tell it to ignore missing LV's? > > vgexport + vgimport should do it for you if none of the > other LV's stretched onto the dead drive. > > If you don't want to spread data across drives that are > not maintained with some sort of RAID then you are > probably better off putting the drives in separate VG's > so that data doesn't accidentally spill across the disks. > > > -- > Steven Lembark 2930 W. Palmer > Workhorse Computing Chicago, IL 60647 > +1 773 252 1080 > > _______________________________________________ > linux-lvm mailing list > linux-lvm@sistina.com > http://lists.sistina.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ -- =========================== Daniel Wittenberg Senior Unix Admin University of Iowa - ITS _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
