|
|||||||
| Forums | Search Forums | Register | Forum Rules | Man Pages | Albums | FAQ | Members | Calendar | Search | Today's Posts | Mark Forums Read |
| AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace. |
|
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||
|
||||
|
importvg question
Is there a way to find the volume group name after assigning hdisk to the machine for importing it ? Code:
importvg -y <find_the_name_from_the_unknown_disk_> hdiskX
Last edited by zaxxon; 02-05-2013 at 06:35 AM.. Reason: code tags and separating to own thread |
| Sponsored Links | ||
|
|
#2
|
||||
|
||||
|
The VG name is stored in the ODM, not on a disk. On the disk is only the VGDA which has the VGID stored. You can use the following to read the VGDA before importing it: Code:
lqueryvg -tcAp <hdisk> It reads all information about the VGDA directly from the disk. There is a part starting with "Logical:" which shows the LVs on this disk. The long number is the VGID, at least the part before the dot. Why do you need to use the VG name from the former disk? To check the contents of the disk you could always import it with any name but a VG name that already exists. Last edited by zaxxon; 02-05-2013 at 06:59 AM.. |
| Sponsored Links | ||
|
|
#3
|
|||
|
|||
|
Thanks Zaxxon for the reminder.
Sometimes importing a volume group, which has same Logical volume names would rename it by itself. To avoid renaming of the logical volumes, is it possible to know the contents ( logical volumes + filesystems + volume group name ) before importing. |
|
#4
|
||||
|
||||
|
The reminder vanishes in a month.
When the LVs already exist, you will always have to rename them, either by the automatic mechanism you described or by yourself manually before doing the import. Anyway, you should be able to read the LV names the way I have described before the import. If it is a cluster, VG names and LV names have to be unique in the whole cluster. If it is a kind of rescue import, maybe choose some test box to avoid a mess up of names. If you can get the ODM files from a restore of the box where this PV/VG originally belonged too, you could get it from there by examining the ODM files. |
| Sponsored Links | ||
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| A question | Abhijeet_Atti | Shell Programming and Scripting | 18 | 02-08-2012 02:25 AM |
| Unable to execute varyonvg during importvg | dantares | AIX | 3 | 02-24-2010 02:39 AM |
| OS Question | IBravo | AIX | 1 | 06-26-2008 06:21 PM |
| nooB questions on importvg and exportvg | outtacontrol | AIX | 1 | 02-15-2007 08:19 PM |
|
|