map file.

[Waugh]

Hi,

Pls any one describe in one line what is map file.whats its contains

Reagrds
Rkumar

[Patrick Wallek]

Have a read through the 'vgexport' man page, specifically the '-m' option.

If you still have questions after that, post back again.

http://docs.hp.com/en/B2355-60130/vgexport.1M.html

[Waugh]

Hi Patric,

I know it. -m its maps the logical volume.
-s for VGID.but what will happen if i exported the the without -m switch.which lv name it will take.

Regards
Rkumar

[rajv]

a lack of documentation makes it shady.

However, System.map is an actual file on your filesystem. When you compile a new kernel, your old System.map has wrong symbol information. A new System.map is generated with each kernel compile and you need to replace the old copy with your new copy.

In Volume Group

Map file is take a shadow of the volume. It contains all the details of the VG.
we can export that to any other server.

[Ninad_1 · Accepted solution]

Hi,

If you use -m option - the map file will contain the names of the lvols , if you had not created map file with -m and then import the VG the lvols will get the same name with which you created it (you have to give the disks which constitue the VG).
If you import without providing map file, then the lvol names will be lvol1 , lvol2, lvol3 ...

With -s option the map file also contains the VGID for the VG
When you use the map file created with -s option while importing, then all the disks connected to the server are scanned to check which all disks have the VGID mentioned in th map file and thus you do not have to give the disks which constitute the VG while importing the VG

You can safely try creating map file with -m and -s options by using the -p option along with them (which will create the map file but will not export the VG)
e.g
vgexport -p -v -m mapfile1 /dev/vgname
vgexport -p -v -s mapfile2 /dev/vgname


Regards,
Ninad