vgremove question

[ConnieK]

Devender,

I did the vgchange on both vgtest and vgtst - both reported:
# vgchange -a y /dev/vgtest2
vgchange: Volume group "/dev/vgtest2" does not exist in the "/etc/lvmtab" file.
# vgchange -a y /dev/vgtst
vgchange: Volume group "/dev/vgtst" does not exist in the "/etc/lvmtab" file.

So since they are not there, should I just rm -r /dev/vgtest2 & /dev/vgtst or do I need to do a vgexport or something else - like a vgremove?

[erics_1 · Accepted solution]

If neither volume group is listed in the lvmtab, rm -r both volume group entries. Afterwards, do your mkdir/mknod and attempt vgimport once again.

Regards,
Eric

[ConnieK]

Eric - HOOYAH!!!! Did exactly what you said. Look at the results:

vgimport: Warning: Volume Group contains "7" PVs, "14" specified. Continuing.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.

The instructions in the document state that I need to "determine the previous name of the volume group by mounting the filesystems and viewing the content." How can I do that when I have no idea what the filesystems were?

[ConnieK]

Ok - so now I did:
# vgchange -a y /dev/vgtest
Activated volume group
Volume group "/dev/vgtest" has been successfully changed.

Then, I did:
# vgdisplay -v /dev/vgtest
--- Volume groups ---
VG Name /dev/vgtest
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 7
Act PV 7
Max PE per PV 3473
VGDA 14
PE Size (Mbytes) 4
Total PE 24304
Alloc PE 24300
Free PE 4
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vgtest/lvol1
LV Status available/syncd
LV Size (Mbytes) 97200
Current LE 24300
Allocated PE 24300
Used PV 7


--- Physical volumes ---
PV Name /dev/dsk/c34t5d4
PV Name /dev/dsk/c37t5d4 Alternate Link
PV Status available
Total PE 3472
Free PE 0
Autoswitch On

PV Name /dev/dsk/c34t5d5
PV Name /dev/dsk/c37t5d5 Alternate Link
PV Status available
Total PE 3472
Free PE 0
Autoswitch On

PV Name /dev/dsk/c34t5d6
PV Name /dev/dsk/c37t5d6 Alternate Link
PV Status available
Total PE 3472
Free PE 0
Autoswitch On

PV Name /dev/dsk/c34t5d7
PV Name /dev/dsk/c37t5d7 Alternate Link
PV Status available
Total PE 3472
Free PE 4
Autoswitch On

PV Name /dev/dsk/c34t8d0
PV Name /dev/dsk/c37t8d0 Alternate Link
PV Status available
Total PE 3472
Free PE 0
Autoswitch On

PV Name /dev/dsk/c34t8d1
PV Name /dev/dsk/c37t8d1 Alternate Link
PV Status available
Total PE 3472
Free PE 0
Autoswitch On

PV Name /dev/dsk/c34t8d2
PV Name /dev/dsk/c37t8d2 Alternate Link
PV Status available
Total PE 3472
Free PE 0
Autoswitch On


So, now it's all there, but again, how can I determine what the previous name of the volume group was?

[Pete Randall]

Constance,

I don't think there is any way to tell the previous name. Now that you've imported it as vgtest, that's what it's known as. The only way to find out a previous name would be to find some hardcopy documentation of the system.


Pete

[ConnieK]

Well shoot! Thought there was a magical something somewhere....

So, could these actually be "ghosts" from the migration process? Maybe they were just temporary?

[erics_1]

Constance,

This vg only had one lvol at 97gb in size. Since you vgimported without a mapfile, the lvol name wasn't necessarily lvol1. This is the naming convention LVM uses by default. You may be able to determine the old vg name by looking at a backed up copy of /etc/lvmtab before the volume group was initially wiped out. You could compare the disks in vgtest with those in the backup copy.

Good Luck,
Eric