"...U have huger swap and compared to memory, what is the application you are running...."
Sorry, I don't see the relevance.
"...if the additional swap lvols are on the same disk, the io will kill your server...."
Sorry, only to a point and because the o/s is also in vg00, else, io will be constant as 2ndary swap is written too in round robin order and not in parallel.
Going up: lvol2>lvol3>lvol7>lvol8
Going down: lvol8>lvol7>lvol3>lvol2
a) first reboot the server since you no longer have any memory
b) 2nd add more swap, another vg then vg00 would be preferred since the o/s is always the busiest disk. In the future, separate all your 2ndary swap from vg00 and onto another vg with other disks, then you'll be getting more spindles involved
c) Check for a memeory leak using this procedure:
1) 15 to 20 minute cron until id'd memeory leak
2) UNIX95=1 ps -ef -o vsz,pid,ppid,state,wchan,comm | sort -rn | head -15 >> /dir/outfile
Note: Put this into a script and add some headers and $DATE's with timestamps to make a readable report
3) Check the report from day to day, note any growth in the first column, the vsz column. A growing vsz will id the pid and ppid with the memory leak.
Support Fatherhood - Stop Family Law
