On Tue, Jan 28, 2003 at 11:47:24AM +0100, Heinz J . Mauelshagen wrote: > b. you implement LVM2/device-mapper and run "vgscan ; vgchange -P -ay", which > will activate your VG without the missing drive. This solution enables > you to retrieve the data still accessable _but_ won't let you change > your volume group configuration. We are working on an enhancement supporting > such changes. So far, 'vgreduce --removemissing' is in CVS; this removes everything necessary to make a VG consistent again after losing disk(s). If *any* part of an LV is missing, the *entire* LV gets deleted, so you should ensure you've made a copy of anything you want to retain first. Running first with '--test' shows you which LVs would get deleted. Alternatively, if you have replacement disk(s), you can use pvcreate & vgcfgrestore to put it into the VG in place of the one(s) lost. Or if you want to do anything differently, you can edit the metadata in text form and use vgcfgrestore to effect your changes. Alasdair -- agk@uk.sistina.com _______________________________________________ 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/
