vg issue

[raymond cavanaugh_2]

We had to create a vg for a couple of new directories for an Oracle migration. This caused problems with the /dev/vg### in not allowing us to remove the created vg's which once created in conflict would not show up under the file systems and disk in SAM. I was able to fix this problem, by manually going into the /dev directory and dropping all of the vg(s) I created in SAM. But after a reboot in this process, one of the vg(s) which we do use was dismounted and deactivated from SAM. I checked the /etc/fstab and the vg(s) which I commented out are disabled, but also one I did not is also disabled in SAM.
What I need to know is how do I get SAM to re-activate the vg in question?

[A. Clay Stephenson]

You didn't quite do the required steps. Your /etc/lvmtab still has entries in it. You need to do a vgexport /dev/vgxx. This will remove the /dev/vgxx/* entries and, in addition, remove the corresponding entries in /etc/lvmtab. Do a "strings /etc/lvmtab" and see if your VG is still in lvmtab. The good news is that vgexport will still work eventhough you have manually removed the device nodes and directory under /dev.

[Steven E. Protter]

vgimport will bring the vg configuration information back in and allow you to activate the volume group as follows:

vgchange -a y vg##

To make a volume group go away the command is vgexport.

Prior to doing this if its to go away forever use lvremove to remove all of the logcial volumes.

SEP

[Nguyen Anh Tien]

You are wrongs in removing vg
If you want to remove let use
#lvremove lvname - all lv on vg
#vgremove vgname pvname
OR
#vgexport vgname.
DO NOT REMOVE FOLDER ONLY. VG INFOR STILL KEEP IN /ETC/FSTAB.

[Isralyn Manalac_1]

You need to "export" the vgs from the /etc/lvmtab file using vgexport. Use vgimport to put the vg back into the lvmtab file.

Regards,

Isralyn