1748164 Members
3732 Online
108758 Solutions
New Discussion юеВ

Re: maxswapchunk problem

 
newunix
Frequent Advisor

maxswapchunk problem

ver ii1 v1

server got rebooted and in syslog we got this alert..

vmunix: Unable to add all swap for device: /dev/vg00/lvol11. Increase the tunable parameter maxswapchunks by 6144 and re-configure your system..

attached the output of vgdisplay and pvdisplay ..

so how can we proceed now
4 REPLIES 4
Suraj K Sankari
Honored Contributor

Re: maxswapchunk problem

Hi,

As per the log "swapinfo -tam"
its looks your swap device dev/vg00/lvol11 is up.

Suraj
Steven E. Protter
Exalted Contributor

Re: maxswapchunk problem

Shalom,

Looks like you added 20 GB of swap to the system.

LV Name /dev/vg00/secswap

LV Status available/syncd

LV Size (Mbytes) 20480

Current LE 1280

Allocated PE 2560

Used PV 2

Now with sam or kmtune/kctune increase the parameter indicated in the message and reboot again so the swap is recognized.

swapinfo -tam would be helpful in seeing why it was necessary to go from 4 GB of swap to 24 GB of swap.

It would also tell us how much memory is in your system, which would allow us to advise you an a good swap number.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Patrick Wallek
Honored Contributor

Re: maxswapchunk problem

Do what it says and increase teh 'maxswapchunks' kernel parameter by 6144.

I always max this out to 16384.
newunix
Frequent Advisor

Re: maxswapchunk problem

LV Name /dev/vg00/lvol11
LV Status available/syncd
LV Size (Mbytes) 20480
Current LE 1280
Allocated PE 2560
Used PV 2

apart from secswap lv ,, we have lvol1 for swap.
both entries has been made in fstab

so total we are having 40 gb of swap space.

when we discused with back end team they are saying this is not a problem..

my doubt is will it affect anything..