eviem
asked on
AIX 6.1: need to grow single SAN disk rootvg, does this require a downtime?
I have been getting this message in the errpt alot:
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
E87EF1BE 0622150016 P O dumpcheck The largest dump device is too small.
normally, I would add couple PPs to the dumplv and that fixes the issue.
However, I am very low on space in rootvg and will be requesting another disk from the SAN team to grow rootvg. The question is that I am on AIX 6100-03-04-1014 and not sure if I can just add the new disk and grow my vg without a downtime, or I will have to take a downtime, add the bigger new disk and migrate the data on the old disk to the new disk. I am fairly new to AIX, so your directives will be greatly appreciated. Thanks in advance!
Additional info:
serve_her_right[/] ># lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00c24dd000004c000000011a4e
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 641 (10256 megabytes)
MAX LVs: 256 FREE PPs: 3 (48 megabytes)
LVs: 12 USED PPs: 638 (10208 megabytes)
OPEN LVs: 11 QUORUM: 2 (Enabled)
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
serve_her_right[/] ># lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 2 2 1 closed/syncd N/A
hd8 jfs2log 1 1 1 open/syncd N/A
hd6 paging 144 144 1 open/syncd N/A
hd9var jfs2 77 77 1 open/syncd /var
hd3 jfs2 64 64 1 open/syncd /tmp
hd4 jfs2 50 50 1 open/syncd /
hd2 jfs2 145 145 1 open/syncd /usr
hd1 jfs2 32 32 1 open/syncd /home
hd10opt jfs2 31 31 1 open/syncd /opt
fslv08 jfs2 4 4 1 open/syncd /storix
lg_dumplv sysdump 72 72 1 open/syncd N/A
livedump jfs2 16 16 1 open/syncd /var/adm/ras/livedump
serve_her_right[/] ># lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 641 3 00..00..00..00..03
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
E87EF1BE 0622150016 P O dumpcheck The largest dump device is too small.
normally, I would add couple PPs to the dumplv and that fixes the issue.
However, I am very low on space in rootvg and will be requesting another disk from the SAN team to grow rootvg. The question is that I am on AIX 6100-03-04-1014 and not sure if I can just add the new disk and grow my vg without a downtime, or I will have to take a downtime, add the bigger new disk and migrate the data on the old disk to the new disk. I am fairly new to AIX, so your directives will be greatly appreciated. Thanks in advance!
Additional info:
serve_her_right[/] ># lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 00c24dd000004c000000011a4e
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 641 (10256 megabytes)
MAX LVs: 256 FREE PPs: 3 (48 megabytes)
LVs: 12 USED PPs: 638 (10208 megabytes)
OPEN LVs: 11 QUORUM: 2 (Enabled)
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
serve_her_right[/] ># lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 2 2 1 closed/syncd N/A
hd8 jfs2log 1 1 1 open/syncd N/A
hd6 paging 144 144 1 open/syncd N/A
hd9var jfs2 77 77 1 open/syncd /var
hd3 jfs2 64 64 1 open/syncd /tmp
hd4 jfs2 50 50 1 open/syncd /
hd2 jfs2 145 145 1 open/syncd /usr
hd1 jfs2 32 32 1 open/syncd /home
hd10opt jfs2 31 31 1 open/syncd /opt
fslv08 jfs2 4 4 1 open/syncd /storix
lg_dumplv sysdump 72 72 1 open/syncd N/A
livedump jfs2 16 16 1 open/syncd /var/adm/ras/livedump
serve_her_right[/] ># lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk1 active 641 3 00..00..00..00..03
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Also, if this TL version of AIX (6100-03-04-1014 ) does not hinder me from growing rootvg without a downtime, I would rather ask the SAN team to grow the existing disk instead of getting a new disk. Does anyone know the cut off version of the AIX OS where a downtime is absolutely necessary to grow rootvg? Thanks again!
Adding a new disk to rootvg does not require any downtime,
that's the case since AIX 4.something.
No need to worry, AIX 6 supports it at any level.
If the new disk is behind a VIOS doesn't matter at all.
The LPAR must see it (which requires proper setup on VIOS, of course), that's all.
Growing an existing disk in rootvg is supported starting with AIX 6.1 TL 4, which means: not on your machine!
The required steps to add a new disk to rootvg are already described in my first comment.
that's the case since AIX 4.something.
No need to worry, AIX 6 supports it at any level.
If the new disk is behind a VIOS doesn't matter at all.
The LPAR must see it (which requires proper setup on VIOS, of course), that's all.
Growing an existing disk in rootvg is supported starting with AIX 6.1 TL 4, which means: not on your machine!
The required steps to add a new disk to rootvg are already described in my first comment.
ASKER
Thanks a million!
You're welcome!
ASKER
My original question was answered, but I have a follow-up question. I understand that I can add a new disk and extend it as part of my rootvg with no downtime, but I cannot grow my single existing disk because of the TL limitations.
I was just informed that we use single disk for rootvg, which means that once the new disk is extended, I will have to migrate the data on the old disk to the new. Yes, it is a downtime.
What are the correct steps to remove the old disk so that I can return it to the SAN team?
I was just informed that we use single disk for rootvg, which means that once the new disk is extended, I will have to migrate the data on the old disk to the new. Yes, it is a downtime.
What are the correct steps to remove the old disk so that I can return it to the SAN team?
Is it an option for you to have two disks in rootvg for a short amount of time?
If so you could easily mirror the LVs of the first, smaller disk to the new, bigger one to then unmirror again, keeping the bigger disk. Once this is done you can remove the old disk from rootvg and return it to your SAN people. If we do all this thoroughly you won't have any downtime.
If so you could easily mirror the LVs of the first, smaller disk to the new, bigger one to then unmirror again, keeping the bigger disk. Once this is done you can remove the old disk from rootvg and return it to your SAN people. If we do all this thoroughly you won't have any downtime.
ASKER
Yes, I can have two disk in vg for some time! This would be the ideal option if I can do what you are suggesting. I will further explore this option on a test box first. Again, thanks! I will provide feedback
Please familiarize yourself with the commands "mirrorvg" and "unmirrorvg", also "savebase" "chpv -c", "bosboot" and "bootlist"
Good luck!
Good luck!
ASKER
After all was said and done, I was given an additional disk by the SAN team. I followed your directions and am now using 2 hdisks in my rootvg
ASKER