Problem removing a Volume Group

[dictum9]

Any idea how to proceed? It complains about lvols, but I don't see any.


#: vgremove /dev/vgignite
vgremove: Volume group "/dev/vgignite" still contains a logical volume(s).
vgremove: Couldn't remove volume group "/dev/vgignite".
#:


#: vgdisplay -v /dev/vgignite
--- Volume groups ---
VG Name /dev/vgignite
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 3975
VGDA 2
PE Size (Mbytes) 4
Total PE 3974
Alloc PE 3584
Free PE 390
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0


--- Physical volumes ---
PV Name /dev/dsk/c10t0d0
PV Status available
Total PE 3974
Free PE 390
Autoswitch On

[Patrick Wallek · Accepted solution]

Your "Cur LV" still shows 1. Your "Free PE" on the drive is 390 and "TOTAL PE" is 3974. If there were no LVOLs configured the FREE PE should be the same as the TOTAL PE.

Do a 'strings /etc/lvmtab | more' and look for the section for this VG. See if an LV is listed.

If you really want to get rid of this VG and are absolutely sure it is not in use, do:

# vgexport /dev/vgignite

That should completely remove it.

[Tim Nelson]

any errors being displayed that you are not posting.. The vgdisplay shows 1 Cur LV..

try a vgexport -p -m /tmp/map.file and review the map file.

If you are absolutely sure nothing is there then vgexport .. Be carefull here before you choose the brute force approach. The system is usually right.

[dictum9]

#: strings /etc/lvmtab
/dev/vg00
/dev/dsk/c2t0d0
/dev/dsk/c2t2d0
/dev/vgignite
/dev/dsk/c10t0d0
/dev/vgignite2
?EFH!
/dev/dsk/c10t1d0
/dev/dsk/c10t0d7

[Steven E. Protter]

Shalom,

There are still logical volumes on this disk.

Since a disk can only be in one volume group, I'd conclude that lvremove is not complete.

pvdisplay -v /dev/dsk/c10t0d0 and get those logical volumes out of there.

Otherwise, vgexport.

Because Ignite is very concerned with restorability, it will not complete on systems with lvm problems.

It may seem like a pain, but it insures as best as you can that the thing will work when you need it.

SEP

[dictum9]

# vgexport /dev/vgignite



that's what I was looking for.
Not sure where the inconsistency showed up from, probably from deleting something in the wrong way.

[CHAKRADHAR_1]

Hi

run vgexport /dev/vgignite

this will resolve the issue & it is safe too.