[linux-lvm] initializing a PV, which was part of an old VG

Alexander Lyakas alex.bolshoy at gmail.com
Thu Oct 6 08:47:39 UTC 2011


yes, I only had a single PV, and I did pvcreate on it, and then
lvm_scan() from my process.

So you suggest to use first pvremove and then pvcreate? Because
pvcreate I do in any case. So pvcreate alone is not similar to
pvremove followed by pvcreate?

If I use -ff, does it do things differently, than if I would call
pvremove/pvcreate without -ff? Should I do first without -ff and use
-ff only if the former fails?


On Wed, Oct 5, 2011 at 9:30 PM, Zdenek Kabelac <zdenek.kabelac at gmail.com> wrote:
> Dne 5.10.2011 17:20, Alexander Lyakas napsal(a):
>> Hello Zdenek,
>> I am frequently hitting issues when trying to create a new VG on a PV
>> that had existing VG. (This PV is usually an MD raid0 or raid1
>> device). I am wondering what is the correct procedure to completely
>> wipe out any remains of LVM signatures from a PV, and initialize the
>> PV afresh?
> util-linux comes with  wipefs  - to wipe fs & raid signatures
> pvremove should wipe label of LVM device - so it should not be recognized as
> PV.
> You may try to use blkid to see how is the device recognized.
>> Here is what I do: for each new VG, I use a new GUID as part of its
>> name, to avoid VG name conflicts.
>> To try to handle the old VG, the VG creation code first calls
>> lvm_vg_name_from_device(pv_name). If it founds a VG there and succeeds
>> to open it, it goes over its LVs, and tries to deactivate them and
>> then removes them. Finally, the code removes the old VG itself. In
>> some cases, however, the code fails to open the old VG, so it
>> proceeds.
> removal of VG doesn't wipe PV headers
>> Next thing I call pvcreate (fork/exec) to initialize the PV (I always
>> use --force twice). After this is completed, I do lvm_scan(), because
> Using -ff is probably a problem here - it's supposed to only used in case
> you really need it - it's not a 'nice' option.
> So first  vgremove  the VG which occupies your PVs - then pvremove should
> work
> without -ff.
>> - pvcreate(/dev/md2) output:
>>        Physical volume "/dev/md2" successfully created
>>        Couldn't find device with uuid
>> NCtRLE-1ffs-GLaH-MYNS-d1hk-ikAt-7dbhm0.
>>        Writing physical volume data to disk "/dev/md2"
>> After lvm_scan(),lvm_vg_create(pool_9644BCB5D4704164976DBD85E471EAAA),
>> lvm_vg_extend(), lvm_vg_write(), the syslog shows:
>> Wiping cache of LVM-capable devices
>> get_pv_from_vg_by_id: vg_read_internal failed to read VG
>> pool_74C7247AE06F4B7DAC557D9A1842EEBD
>> Adding physical volume '/dev/md2' to volume group
>> 'pool_9644BCB5D4704164976DBD85E471EAAA'
>> Creating directory "/etc/lvm/archive"
>> Archiving volume group "pool_9644BCB5D4704164976DBD85E471EAAA"
>> metadata (seqno 0).
>> While pool_74C7247AE06F4B7DAC557D9A1842EEBD is yet some other old VG.
>> At this point the VG seems to be created ok. But later, when I try to
>> create first LV, syslog shows:
>> Wiping cache of LVM-capable devices
>> Couldn't find device with uuid NCtRLE-1ffs-GLaH-MYNS-d1hk-ikAt-7dbhm0.
>> Couldn't find device with uuid NCtRLE-1ffs-GLaH-MYNS-d1hk-ikAt-7dbhm0.
>> There are 1 physical volumes missing.
>> Cannot change VG pool_9644BCB5D4704164976DBD85E471EAAA while PVs are
>> missing.
>> Consider vgreduce --removemissing.
> Have you pvremove-d all PV devices ?
> Zdenek

More information about the linux-lvm mailing list