Multiple Alternate rootvg Criteria

Answer

Multiple altinst_rootvg criteria

01- The current rootvg and physical volumes information are the following
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 639 35 00..02..00..19..14

# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 none None
hdisk2 none None

# bootlist -om normal
hdisk0 blv=hd5 pathid=0

# bootinfo -b
hdisk0

02- Creating the first altinst_rootvg at hdisk1:
# alt_disk_copy -d hdisk1
Calling mkszfile to create new /image.data file.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5.
Creating logical volume alt_hd6.
Creating logical volume alt_hd8.
Creating logical volume alt_hd4.
Creating logical volume alt_hd2.
Creating logical volume alt_hd9var.
Creating logical volume alt_hd3.
Creating logical volume alt_hd1.
Creating logical volume alt_hd10opt.
[..]
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk1 blv=hd5

# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 00050a85ebb2b46a altinst_rootvg
hdisk2 none None

# bootlist -om normal
hdisk1 blv=hd5 pathid=0

03- We will rename altinst_rootvg which is located on hdisk1, since we cannot
Create another one on hdisk2 beacuse of the existing current one on hdisk1:

# alt_rootvg_op -v mash_rootvg
# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 00050a85ebb2b46a mash_rootvg
hdisk2 none None

04- Trying again to create another altinst_rootvg on hdisk2:
# alt_disk_copy -d hdisk2
Calling mkszfile to create new /image.data file.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5.
Creating logical volume alt_hd6.
Creating logical volume alt_hd8.
Creating logical volume alt_hd4.
Creating logical volume alt_hd2.
Creating logical volume alt_hd9var.
Creating logical volume alt_hd3.
Creating logical volume alt_hd1.
Creating logical volume alt_hd10opt.
[..]
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk2 blv=hd5

# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 00050a85ebb2b46a mash_rootvg
hdisk2 00050a85ebd068ab altinst_rootvg

05- Waking up and sleeping altinst_rootvg located on hdisk2:
# alt_disk_install -W hdisk2
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the
alt_rootvg_op man page and documentation for more details.
Executing command: /usr/sbin/alt_rootvg_op -W -d hdisk2
+-----------------------------------------------------------------------------+
Waking up altinst_rootvg volume group ...

# lsvg -o
altinst_rootvg
rootvg

# lsvg -l altinst_rootvg
altinst_rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
alt_hd5 boot 2 2 1 closed/syncd N/A
alt_hd6 paging 32 32 1 closed/syncd N/A
alt_hd8 jfs2log 1 1 1 open/syncd N/A
alt_hd4 jfs2 17 17 1 open/syncd /alt_inst
alt_hd2 jfs2 160 160 1 open/syncd /alt_inst/usr
alt_hd9var jfs2 43 43 1 open/syncd /alt_inst/var
alt_hd3 jfs2 67 67 1 open/syncd /alt_inst/tmp
alt_hd1 jfs2 64 64 1 open/syncd /alt_inst/home
alt_hd10opt jfs2 44 44 1 open/syncd /alt_inst/opt
alt_hd11admin jfs2 8 8 1 open/syncd /alt_inst/admin
alt_lg_dumplv sysdump 64 64 1 closed/syncd N/A
alt_livedump jfs2 16 16 1 open/syncd /alt_inst/var/adm/ras/livedump
alt_auditlv jfs2 64 64 1 open/syncd /alt_inst/audit

# alt_disk_install -S hdisk2
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the
alt_rootvg_op man page and documentation for more details.
Executing command: /usr/sbin/alt_rootvg_op -S hdisk2
+-----------------------------------------------------------------------------+
Putting volume group altinst_rootvg to sleep ...
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/home
forced unmount of /alt_inst/audit
forced unmount of /alt_inst/audit
forced unmount of /alt_inst/admin
forced unmount of /alt_inst/admin
forced unmount of /alt_inst
Fixing LV control blocks...
Fixing file system superblocks...

06- Waking up mash_rootvg located on hdisk1:
# alt_disk_install -W hdisk1
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the
alt_rootvg_op man page and documentation for more details.
Executing command: /usr/sbin/alt_rootvg_op -W -d hdisk1
+-----------------------------------------------------------------------------+
0505-138 alt_disk_install: A wake-up cannot be performed on
volume group: mash_rootvg
alt_rootvg_op: 0505-233 Volume group altinst_rootvg already exists.
You may rename the current altinst_rootvg volume group using
the -v option, then retry the command.

** As per this;
- mash_rootvg (renamed altinst_rootvg) cannot be waken up until it gets a name of: altinst_rootvg.
- If we try booting from mash_rootvg, it will boot and will not report/understand anything about
altinst_rootvg which is located on hdisk2 - beacuse rootvg and mash_rootvg are the same,
And mash_rootvg has been created before creating altinst_rootvg of hdisk2.

07- Attempt booting from mash_rootvg located on hdisk1
# bootlist -m normal hdisk1
# bootlist -om normal
hdisk1 blv=hd5 pathid=0

# shutdown -r
<REBOOTING>

# bootinfo -b
hdisk1

# lspv
hdisk0 00050a85d7342530 old_rootvg
hdisk1 00050a85ebb2b46a rootvg active
hdisk2 00050a85ebd068ab None

08- A wake up and sleep against old_rootvg located on hdisk0 has been done,
So naming has been changed - expectedly - after a wakeup and sleep:
# lspv
hdisk0 00050a85d7342530 altinst_rootvg
hdisk1 00050a85ebb2b46a rootvg active
hdisk2 00050a85ebd068ab None

09- Attempting to rename the current altinst_rootvg located on hdisk0:
# alt_rootvg_op -v new_rootvg -d hdisk0
# lspv
hdisk0 00050a85d7342530 new_rootvg
hdisk1 00050a85ebb2b46a rootvg active
hdisk2 00050a85ebd068ab None

10- Now we can create another altinst_rootvg on hdisk2
(It will definitely know about rootvg on hdisk1, and new_rootvg on hdisk0).
# alt_disk_copy -d hdisk2
Calling mkszfile to create new /image.data file.
Checking disk sizes.
Creating cloned rootvg volume group and associated logical volumes.
Creating logical volume alt_hd5.
Creating logical volume alt_hd6.
Creating logical volume alt_hd8.
Creating logical volume alt_hd4.
Creating logical volume alt_hd2.
Creating logical volume alt_hd9var.
Creating logical volume alt_hd3.
Creating logical volume alt_hd1.
Creating logical volume alt_hd10opt.
[..]
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk2 blv=hd5

# lspv
hdisk0 00050a85d7342530 new_rootvg
hdisk1 00050a85ebb2b46a rootvg active
hdisk2 00050a85ebd068ab altinst_rootvg

11- Booting now from altinst_rootvg located on hdisk2:
# bootlist -om normal
hdisk2 blv=hd5 pathid=0

# shutdown -r now
<REBOOTING>

# bootinfo -b
hdisk2

# lspv
hdisk0 00050a85d7342530 new_rootvg
hdisk1 00050a85ebb2b46a old_rootvg
hdisk2 00050a85ebd068ab rootvg active

12- If booting back from renamed one (new_rootvg located on hdisk0 - which
Was the original rootvg previously and it has all ODM information regarding
The VGs of hdisk1, and hdisk2.
i.e: The VG's of hdisk1, and hdisk2 have been created while the server
Is up from hdisk0.

# bootlist -m normal hdisk0

# shutdown -r now
<REBOOTING>

# bootinfo -b
hdisk0

# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 00050a85ebb2b46a mash_rootvg
hdisk2 00050a85ebd068ab altinst_rootvg

13- Removing all alternate VG's:
# alt_disk_install -X
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the
alt_rootvg_op man page and documentation for more details.
Executing command: /usr/sbin/alt_rootvg_op -X
+-----------------------------------------------------------------------------+
Bootlist is set to the boot disk: hdisk0 blv=hd5

# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 00050a85ebb2b46a mash_rootvg
hdisk2 00050a85ebd068ab None

The above has removed the one named altinst_rootvg. If we want to remove
mash_rootvg, we will have to mention the name:
# alt_disk_install -X mash_rootvg
+-----------------------------------------------------------------------------+
ATTENTION: calling new module /usr/sbin/alt_rootvg_op. Please see the
alt_rootvg_op man page and documentation for more details.
Executing command: /usr/sbin/alt_rootvg_op -X mash_rootvg
+-----------------------------------------------------------------------------+

# lspv
hdisk0 00050a85d7342530 rootvg active
hdisk1 00050a85ebb2b46a None
hdisk2 00050a85ebd068ab None



Thank you very much for taking the time to read through this document.
I hope it has been helpful and easy read. If you feel you have found any inconsistencies,
Please don’t hesitate to email me at ahdmashr@eg.ibm.com

Ahmed Mashhour