On Monday 13 February 2006 08:36, Matthew Plante wrote: > The solution I ended up with was actually to add a new disk and make new > PVs with the same uuid, which wasn't exactly the solution I was going for, > but it ended up working out. I wasn't able to get the --removemissing > option in vgreduce to work for the scenario I mentioned before. > The test scenario I was going for was an unexpected removal of a disk, > where I could remove the disk from the vg, and bring the vg back up in a > semi-working state, minus one disk/some data. I know this is sort of late in the game as you have found a solution that works, but did you ever try using vgreduce -A n vgname pvname? Or the same, but with a force option? I know you said --removemissing didn't work, but that may have been due to not setting -A n. -- Zac Slade _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
