sar -v output.

[Rudi Swennen_1]

Hello,

at work I have a unix system: HP-UX tensing B.10.20 A 9000/800 2000247853 two-user license. Since 2 day he's giving errors like: 10/03/3001 - 18:35
Out of memory during request for 8216 bytes, total sbrk() is 1253640 bytes!

11/03/2003 - 10:34
Out of memory during request for 1016 bytes, total sbrk() is 49416 bytes!
fork: Not enough space.
And when I execute sar -v 1 1 this output is generated:
15:05:09 text-sz ov proc-sz ov inod-sz ov file-sz ov
15:05:10 N/A N/A 376/2068 0 2884/2884 0 1521/4418 0.
Is the inode-size correlated to the memmory problems? Is it normal that the inode-size actual and max are alike?

Thanks,

Rudi

[Stefan Farrelly]

Yes, its normal the inode-size actual and max are the same - its a cache table to the closer to the max the actual is the better the performance.

Your error fork: not enough space
means you have run out of swap space. Check with swapinfo -mt
Youve probably run out of memory first, now out of swap. You should add some more swap or close down some processes that are using lots of memory.

[David_246]

Hoi Rudi,

I attached a program I use for determing the use of swap and claimed memory.

Regs David

[Steven E. Protter]

Greetings,

I've attached a more general background performance data collection script.

You can modify the data collection window pretty easily. It's production, a mod of womething HP sent me.

SEP

[Sridhar Bhaskarla · Accepted solution]

Hi Rudi,

What is more important is to keep an eye on "ov" column next to each parameter. If it is greater than 1, then there were cases of overflow.

Your sar -v looks good.

You may be running out of swap space. You may not swap but will need enough space to reserve the memory for new processes.

Check your swapinfo -t and see if the "total" is near 100%. If so, you would need to add more swap.

-Sri