cancel
Showing results for 
Search instead for 
Did you mean: 

Importing A Volume group

GTBank IT
Occasional Contributor

Importing A Volume group

Hi all,
Good day. I have a VDisk that was mounted to a rp server and volume group created and activated. some information has been saved on this VG but i lost the defination of the Vg in the lvmtab because the lvmtab was recreated.
How can i re import this volume group without the map file as I do not have a copy of the mapfile and I need the data in the VG.


Regards
3 REPLIES
Torsten.
Acclaimed Contributor

Re: Importing A Volume group

Consider to use vgscan, but use the preview option first.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
GTBank IT
Occasional Contributor

Re: Importing A Volume group

Thanks for your response.
I did the vgscan -p -v and it gave me the output below :

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c15t0d5
/dev/dsk/c16t0d5
/dev/dsk/c62t0d5
/dev/dsk/c63t0d5
James R. Ferguson
Acclaimed Contributor

Re: Importing A Volume group

Hi:

I presume that the volume group in question hasn't been activated on this server since the last reboot. In that case, a 'vgscan' isn't going to update '/etc/lvmtab'. It will assist you in discovery, however.

A mapfile is optional. Without it you will need to specify the physical paths to the physical devices when you do a 'vgimport'. If you don't know, or aren't sure of them you can use 'vgscan -p -v' to discover them. This will not alter the '/etc/lvmtab' since you are doing a (p)review operation.

Given the physical disk device files, the absence of a mapfile only means that logical volume names will be built as the standard default names, "lvol" where is the minor number of the logical volume. If you don't want this nomenclature, you can create a mapfile that looks like:

1 mylvol1
2 mylvol2

...or what ever you want the logical volume names to be.

Regards!

...JRF...

The 'vgimport' will, of course update your '/etc/lvmtab'.

Regards!

...JRF...