[linux-lvm] Removing vg and lv after physical drive has been removed

[Rene C.]

I took the leap and ran

dmsetup remove vg04-vz
dmsetup remove vg04-swap

and it sorted the problem.  No errors, no reboot needed.

Thanks for all the input!

On Sun, Sep 2, 2012 at 10:03 AM, Scott Merrilees <scott at merrilees.net> wrote:
> Reboot would clean all currently loaded state from the kernel / processes.
> Wouldn't clean any state stored on disk.
>
> I am not 100% sure what state is stored where for lvm.
> I guess that since vg04 was self contained on one disk,
> and since we can't see anything about vg04,
> that the vg information in saved on the pv in some form,
> and that importing the vg loads the information and is used to setup
> the device mapper.
>
> If that is the case, then a reboot should clear things up, but also
> the dmsetup remove should clear things up.
>
> If the current state is stored in more than the device mapper, then
> just a dmsetup remove may be insufficient.
>
> If you have the vgs spread over more than 1 pv, then I expect lvm
> would be telling you that it can't find
> various pvs with certain pv_uuids, which is what I've more often seen
> when I've done things myself in the
> wrong sequence.
> --
> Scott Merrilees
>
>
> On Sun, Sep 2, 2012 at 12:41 PM, Rene C. <openvz at dokbua.com> wrote:
>> What difference would it make rebooting the server?
>>
>> To recreate the missing drive/PV I'd need a blank drive right?  I
>> don't have that, the drive was replace with another drive that I just
>> called pv05 and is now active and being used.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/