Page name: DST / DST Global Technologies Documentation / Operating System / AIX / AIX - How to

convert rootvg from small to scalable volume group to support disk big sizes

How to convert rootvg from small to scalable

volume group to support big size disks.
Sometimes convert rootvg from small to scalable is needed on DST Cloud AIX servers environment,
due the TSAM restriction to have only one volume group (rootvg) for AIX cloud servers.
High level steps:
1) Confirm that we have initially a small volume group.
2) Nim Boot into maintenance shell
3) Covert the varyoff rootvg, is possible to varyoff rootvg due we boot from network.
4) Verify boot disk and reboot in normal state.
This process use the NIM fuction: maint_boot enable a machine to boot in maintenance mode, and
assumes that communication between nim and lpar is working propertly.

Now, let's see the detail steps:

1) Confirm that we have initially a small volume group. In this case rootvg reside on hdisk0:
# lspv
hdisk0

00c57cf79503ebd0

# readvgda hdisk0 | grep type .....

rootvg

active

readvgda_type: smallvg vgtype:

0 #

2) From Nim smitty tool, lets select the maint_boot option:

http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-2.png
3) Select the appropiare spot for your lpar:
http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-3.png
4) In a separate terminal, connect to the lpar console:
#dconsole lparname

5) When the boot process on dconsole terminal start, then press:

1 <Enter>

To continue with the maintenance boot process...

http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-5.png
6) Nim Boot into maintenance shell
http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-7.png
7) Once in maintenance shell, import rootvg volume group, and verify the new name (usually vg00),
varyoff the new volume group, and finale execute the coversion.
# lsvg
vg00
#varyoffvg vg00
#chvg -G vg00

http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to

convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-9.png
8) Execute, exportvg to relase vg00 information from ODM:
#exportvg vg00

9) Type exit, to return the previous menu.

#exit

http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to

convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-10.png
10) Select the disk where the rootvg reside:
http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-11.png
11) Access the rootvg volume group, and start a shell:
http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-13.png

12) Verify boot disk and reboot in normal state.

http://knowledge.dst.ibm.com/DST/Technical Documentation/Operating System/AIX/AIX - How to
convert rootvg from small to scalable volume group to support disk big sizes?action=AttachFile&
do=get&target=Screenshot-ruben@oc6301611853_~-14.png
13) After a successful reboot, login and verify changes on rootvg volume group:
# readvgda hdisk0| grep type
readvgda_type: svg

Comparing rootvg information before and after this

procedure:
Before:
# lsvg rootvg
VOLUME GROUP:
rootvg
00c57cf700004c0000000150af279360
VG STATE:
active
VG PERMISSION:
read/write
MAX LVs:
256
LVs:
17
OPEN LVs:
16
TOTAL PVs:
1
STALE PVs:
0
ACTIVE PVs:
1
MAX PPs per VG:
32512
MAX PPs per PV:
1016
LTG size (Dynamic): 256 kilobyte(s)
HOT SPARE:
no
PV RESTRICTION:
none
DISK BLOCK SIZE:
512
#

VG IDENTIFIER:
PP SIZE:
TOTAL PPs:
FREE PPs:
USED PPs:
QUORUM:
VG DESCRIPTORS:
STALE PPs:
AUTO ON:

128 megabyte(s)
799 (102272 megabytes)
674 (86272 megabytes)
125 (16000 megabytes)
2 (Enabled)
2
0
no

MAX PVs:
AUTO SYNC:
BB POLICY:
INFINITE RETRY:
CRITICAL VG:

32
no
relocatable
no
no

After:
# lsvg rootvg
VOLUME GROUP:
rootvg
00c57cf700004c0000000150b14c0186
VG STATE:
active
VG PERMISSION:
read/write
MAX LVs:
256
LVs:
17
OPEN LVs:
16
TOTAL PVs:
1
STALE PVs:
0
ACTIVE PVs:
1
MAX PPs per VG:
32768
LTG size (Dynamic): 256 kilobyte(s)
HOT SPARE:
no

VG IDENTIFIER:
PP SIZE:
TOTAL PPs:
FREE PPs:
USED PPs:
QUORUM:
VG DESCRIPTORS:
STALE PPs:
AUTO ON:
MAX PVs:
AUTO SYNC:
BB POLICY:

128 megabyte(s)
798 (102144 megabytes)
673 (86144 megabytes)
125 (16000 megabytes)
2 (Enabled)
2
0
no
1024
no
relocatable

MIRROR POOL STRICT: off

PV RESTRICTION:
none
DISK BLOCK SIZE:
512
#

INFINITE RETRY: no
CRITICAL VG:
no

Disclaimer: This procedure is meant for emergency cases where rebuilding the LPAR using
a mksysb is not an option, like emergency grow of rootvg and customer can not afford a
downtime. The IBM support only recognizes rootvg in standard form so running this
procedure may impede opening a future PMR related to system issues.

Authors:
Francisco Ruben Jimenez Corzo/Mexico/IBM,
Jorge Fernando Gutierrez Ramirez/Mexico/IBM,

rubenj@mx1.ibm.com
jfgutier@mx1.ibm.com