AIX25
asked on
AIX - Paging space assistance
Need assistance with manipulating the paging space on a server. I currently have 82G of paging space on an internal disk. I need to create new paging space lv on the new san disk and allocate 82G to it. Then change the paging space to 1G located on a local disk. Not sure the correct oder that this needs to been done, I do not want this server to start paging and send alerts out.
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk2 rootvg 16384MB 15 yes yes lv
hd6 hdisk2 rootvg 65536MB 4 yes yes lv
root@server[/]# lspv hdiskpower21
0516-320 : Physical volume hdiskpower21 is not assigned to
a volume group.
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging00 hdisk2 rootvg 16384MB 15 yes yes lv
hd6 hdisk2 rootvg 65536MB 4 yes yes lv
root@server[/]# lspv hdiskpower21
0516-320 : Physical volume hdiskpower21 is not assigned to
a volume group.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Seems that hdiskpower21 is not actually accessible!
What's the output of lsvg -p pagingvg ?
What does lqueryvg -Atp hdiskpower21 say?
Do you get a PVID with lspv |grep hdiskpower21 ?
What do you get with lspv hdiskpower21 ?
What's the output of lsvg -p pagingvg ?
What does lqueryvg -Atp hdiskpower21 say?
Do you get a PVID with lspv |grep hdiskpower21 ?
What do you get with lspv hdiskpower21 ?
ASKER
root@server[/]# lsvg -p pagingvg
0516-306 : Unable to find volume group pagingvg in the Device
Configuration Database.
root@server[/]#
root@server[/]# lqueryvg -Atp hdiskpower21
0516-320 lqueryvg: Physical volume hdiskpower21 is not assigned to
a volume group.
Max LVs: 256
PP Size: 28
Free PPs: 400
LV count: 0
PV count: 1
Total VGDAs: 2
Conc Allowed: 0
MAX PPs per PV 1016
MAX PVs: 32
Quorum (disk): 1
Quorum (dd): 1
Auto Varyon ?: 1
Conc Autovaryo 0
Varied on Conc 0
Physical: 0007bcbbfddf3b33 2 0
Total PPs: 400
LTG size: 128
HOT SPARE: 0
AUTO SYNC: 0
VG PERMISSION: 0
SNAPSHOT VG: 0
IS_PRIMARY VG: 0
PSNFSTPP: 4352
VARYON MODE: ???????
VG Type: 0
Max PPs: 32512
root@server[/]#
root@server[/]# lspv |grep hdiskpower21
hdiskpower21 0007bcbbfddf3b33 None
root@server[/]#
root@server[/]# lspv hdiskpower21
0516-320 : Physical volume hdiskpower21 is not assigned to
a volume group.
root@server[/]#
0516-306 : Unable to find volume group pagingvg in the Device
Configuration Database.
root@server[/]#
root@server[/]# lqueryvg -Atp hdiskpower21
0516-320 lqueryvg: Physical volume hdiskpower21 is not assigned to
a volume group.
Max LVs: 256
PP Size: 28
Free PPs: 400
LV count: 0
PV count: 1
Total VGDAs: 2
Conc Allowed: 0
MAX PPs per PV 1016
MAX PVs: 32
Quorum (disk): 1
Quorum (dd): 1
Auto Varyon ?: 1
Conc Autovaryo 0
Varied on Conc 0
Physical: 0007bcbbfddf3b33 2 0
Total PPs: 400
LTG size: 128
HOT SPARE: 0
AUTO SYNC: 0
VG PERMISSION: 0
SNAPSHOT VG: 0
IS_PRIMARY VG: 0
PSNFSTPP: 4352
VARYON MODE: ???????
VG Type: 0
Max PPs: 32512
root@server[/]#
root@server[/]# lspv |grep hdiskpower21
hdiskpower21 0007bcbbfddf3b33 None
root@server[/]#
root@server[/]# lspv hdiskpower21
0516-320 : Physical volume hdiskpower21 is not assigned to
a volume group.
root@server[/]#
Has this disk been in use by some other volume manager?
Try chpv -C hdiskpower21
If this doesn't return an error retry the mkvg operation using the "-f" flag:
mkvg -f -s 256 -y pagingvg hdiskpower21
Try chpv -C hdiskpower21
If this doesn't return an error retry the mkvg operation using the "-f" flag:
mkvg -f -s 256 -y pagingvg hdiskpower21
ASKER
root@server[/]# chpv -C hdiskpower21
root@server[/]#
root@server[/]# mkvg -s 256 -y pagingvg hdiskpower21
pagingvg
0516-013 /usr/sbin/varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
0516-862 mkvg: Unable to create volume group.
It didn't return no errors when I ran the chpv command.
root@server[/]#
root@server[/]# mkvg -s 256 -y pagingvg hdiskpower21
pagingvg
0516-013 /usr/sbin/varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
0516-862 mkvg: Unable to create volume group.
It didn't return no errors when I ran the chpv command.
You should retry mkvg with the "-f" flag.
I'm really unsure what happens here. Do you see any messages with "errpt"?
I'm really unsure what happens here. Do you see any messages with "errpt"?
ASKER
root@server[/]# mkvg -f -s 256 -y pagingvg hdiskpower21
pagingvg
0516-013 /usr/sbin/varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
0516-862 mkvg: Unable to create volume group.
root@server[/]#
pagingvg
0516-013 /usr/sbin/varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
0516-862 mkvg: Unable to create volume group.
root@server[/]#
There's something badly wrong with this particular disk.
lqueryvg says there are 2 VGDAs (which is normal and sufficient),
but varyonvg complains about "no good copies".
Did you try "errpt"?
I'd suggest removing hdiskpower21: rmdev -dl hdiskpower21
and let the system rediscover it: cfgmgr
Any messages/errors?
lqueryvg says there are 2 VGDAs (which is normal and sufficient),
but varyonvg complains about "no good copies".
Did you try "errpt"?
I'd suggest removing hdiskpower21: rmdev -dl hdiskpower21
and let the system rediscover it: cfgmgr
Any messages/errors?
ASKER
Finally got it working.
Now I ran into this error:
root@server[/]# mkps -s 328 -n -a pagingvg
Paging space limit exceeded. Please specify smaller size.
root@server[/]#
Now I ran into this error:
root@server[/]# mkps -s 328 -n -a pagingvg
Paging space limit exceeded. Please specify smaller size.
root@server[/]#
How did you get it to work?
As for the error - I forgot that there is a paging space size limit of 64 GB per device.
So, with the configured PP size of 256 the limit is 256 PPS.
mkps -s 256 -n -a pagingvg
Since your disk is probably bigger - how about placing your dump device there?
I/O to dump devices only takes place in case of a crash, so the activity of the dump device will not interfere with paging activity.
As for the error - I forgot that there is a paging space size limit of 64 GB per device.
So, with the configured PP size of 256 the limit is 256 PPS.
mkps -s 256 -n -a pagingvg
Since your disk is probably bigger - how about placing your dump device there?
I/O to dump devices only takes place in case of a crash, so the activity of the dump device will not interfere with paging activity.
ASKER
I rmdev'ed hdiskpower21 and hdisk multipaths associated with it, then emc_cfgmgr.
Next error:
root@server[/]# rmps paging00
0517-062 rmps: Paging space paging00 is active.
0517-061 rmps: Cannot remove paging space paging00.
I can't move the dump device. The request was for only ps.
Next error:
root@server[/]# rmps paging00
0517-062 rmps: Paging space paging00 is active.
0517-061 rmps: Cannot remove paging space paging00.
I can't move the dump device. The request was for only ps.
Seems I had an off day yesterday.
Deactivate the paging space with
swapoff paging00
then proceed with rmps.
Deactivate the paging space with
swapoff paging00
then proceed with rmps.
ASKER
root@server[/]# swapoff paging00
0517-081 swapoff: Cannot deactivate paging space paging00.
: A file or directory in the path name does not exist.
0517-081 swapoff: Cannot deactivate paging space paging00.
: A file or directory in the path name does not exist.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, I ran sawoff /dev/paging00. But, its still hanging at the prompt. Not sure if that takes a long time. Whats the next step?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
root@server[/]# lsvg -p rootvg
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 546 93 00..00..00..64..29
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdiskpower21 pagingvg 65536MB 1 yes yes lv
hd6 hdisk2 rootvg 65536MB 4 yes yes lv
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk2 active 546 93 00..00..00..64..29
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdiskpower21 pagingvg 65536MB 1 yes yes lv
hd6 hdisk2 rootvg 65536MB 4 yes yes lv
Perfect.
What is the PP size of rootvg? "lsvg rootvg", the value next to "PP SIZE:"
Subtract the number of MBs (in multiples of the PP size) you'd like to keep in hd6 from 65536,
divide the result by the PP size. That's the number of PPs to remove.
Use this number "x" in
chps -d x hd6
What is the PP size of rootvg? "lsvg rootvg", the value next to "PP SIZE:"
Subtract the number of MBs (in multiples of the PP size) you'd like to keep in hd6 from 65536,
divide the result by the PP size. That's the number of PPs to remove.
Use this number "x" in
chps -d x hd6
ASKER
I think I accidently removed the paging space on hd6? Did I just create myself a new problem? Please help me get hd6 back to normal
root@server[/]# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 0007bcbb0000d6000000011a97 10da69
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (279552 megabytes)
MAX LVs: 256 FREE PPs: 218 (55808 megabytes)
LVs: 17 USED PPs: 874 (223744 megabytes)
OPEN LVs: 16 QUORUM: 1 (Disabled)
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: no
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
root@server[/]# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk3 active 546 125 00..00..00..64..61
hdisk2 active 546 93 00..00..00..64..29
root@server[/]# bootinfo -s hdisk2
140013
root@txcdbsnwh005[/]# chps -d 200 hd6
shrinkps: Temporary paging space paging00 created.
shrinkps: Paging space hd6 removed.
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdiskpower21 pagingvg 65536MB 1 yes yes lv
paging00 hdisk3 rootvg 14336MB 1 yes yes lv
hd6 hdisk2 rootvg 14336MB 0 no no lv
root@server[/]#
root@server[/]# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 0007bcbb0000d6000000011a97
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1092 (279552 megabytes)
MAX LVs: 256 FREE PPs: 218 (55808 megabytes)
LVs: 17 USED PPs: 874 (223744 megabytes)
OPEN LVs: 16 QUORUM: 1 (Disabled)
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: no
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
root@server[/]# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk3 active 546 125 00..00..00..64..61
hdisk2 active 546 93 00..00..00..64..29
root@server[/]# bootinfo -s hdisk2
140013
root@txcdbsnwh005[/]# chps -d 200 hd6
shrinkps: Temporary paging space paging00 created.
shrinkps: Paging space hd6 removed.
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdiskpower21 pagingvg 65536MB 1 yes yes lv
paging00 hdisk3 rootvg 14336MB 1 yes yes lv
hd6 hdisk2 rootvg 14336MB 0 no no lv
root@server[/]#
Did you interrupt the chps process??
chps would have created hd6 anew.
chps would have created hd6 anew.
ASKER
No, I did not interrupt it. I opened another terminal and ran the lsps -a. Paging00 must have been a temp one. Here is my new output:
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdiskpower21 pagingvg 65536MB 1 yes yes lv
hd6 hdisk2 rootvg 14336MB 1 yes yes lv
root@server[/]# lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdiskpower21 pagingvg 65536MB 1 yes yes lv
hd6 hdisk2 rootvg 14336MB 1 yes yes lv
Of course paging00 was temporary. AIX told you so:
shrinkps: Temporary paging space paging00 created.
Now you have hd6 on rootvg with 14 GB and the new paging01 with 64 GB on pagingvg.
It think this is (roughly) what you desired.
shrinkps: Temporary paging space paging00 created.
Now you have hd6 on rootvg with 14 GB and the new paging01 with 64 GB on pagingvg.
It think this is (roughly) what you desired.
ASKER
I would like to have 82G on pagingvg and 1G on hd6. Can you assit...never worked with ps before.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
root@server[/]# mkvg -s 256 -y pagingvg hdiskpower21
pagingvg
0516-013 /usr/sbin/varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
0516-862 mkvg: Unable to create volume group.
root@server[/]#
What are you trying to achieve by placing a new PS on a SAN disk and reducing the existing
PS by nearly the size of the new one?
Right now, we currently have a bunch of processes turned off. We know it probably won't give us significant performance change, but it will help once we turn on the processes and will have more space to expand our ps if needed, where on our current internal disk, its full.