memory usage

[Luca Rasconi]

Hi,
I have a system very slow. I know that the cause is the memory usage (100%). How can i find what processes, and in what percentage, are implicated in this context?

Thank you
Luca

[Pete Randall · Accepted solution]

Luca,

Do you have Glance? If so,
go into the Process List and sort on the Res Mem column. If not, you really should look into getting it - it's an invaluable tool. There's a free trial version available on your application CD's.

Pete

[Stefan Farrelly]

This will list the processes in order of memory usage;

UNIX95= ps -e -o vsz=Kbytes -o ruser -o pid,args=Command-Line | sort -rnk1 | more

[Ravi_8]

Hi,

'top' and 'glance' are tools to monitor

[Luca Rasconi]

Ok. Thanks to your answers i found the reason of the strange behaviour of the machine. Now the question is:
from a line in the syslog:
Dec 3 14:23:46 h3mih022 vmunix: SCSI: Read error -- dev: b 31 0x1d0100, errno: 126, resid: 2048

Somedy can tell me how reach the device file of the disk from 0x1d0100?

Thank you
Luca

[John Poff]

Hi Luca,

Here is a thread that discusses how to decode the device file from a SCSI error:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x6c5f0fe6d0f7d61190050090279cd0f9,00.html


Usually the device has 8 bytes, and your message only lists 6 bytes for the address. Is there just 6 bytes in your error message, or did it just get lost in cutting and pasting into your reply?

JP

[Luca Rasconi]

No, there are only 6 byte.
I don't know why.

Luca

[John Poff]

Luca,

My guess is that with just six bytes, the address 0x1d0100 would decode to c30t0d1. Does that correspond to an acutal device on your system?

Like I said, it's just a guess. :)

JP

[Luca Rasconi]

What's the meaning of this:
[h3mih022]/# iostat

device bps sps msps

c1t2d0 0 0.0 1.0
c2t2d0 0 0.0 1.0
c33t0d1 0 0.0 1.0
c33t0d2 0 0.0 1.0
c33t0d3 0 0.0 1.0
c33t0d4 0 0.0 1.0
c33t0d5 0 0.0 1.0
c33t0d6 0 0.0 1.0
c33t0d7 0 0.0 1.0
0x1f/0x1d0100 0 0.0 1.0
0x1f/0x1d0200 0 0.0 1.0
0x1f/0x1d0300 0 0.0 1.0
0x1f/0x1d0400 0 0.0 1.0
0x1f/0x1d0500 0 0.0 1.0
0x1f/0x1d0600 0 0.0 1.0
0x1f/0x1d0700 0 0.0 1.0
c31t0d1 0 0.0 1.0
c31t0d2 0 0.0 1.0
c31t0d3 0 0.0 1.0
c31t0d4 0 0.0 1.0
c31t0d5 0 0.0 1.0
c31t0d6 0 0.0 1.0
c31t0d7 0 0.0 1.0

[John Poff]

Actually, I haven't had enough caffeine to add hex numbers this morning! 10 in hex is 16 decimal, and d in hex is 13 decimal, so maybe we are looking at 16+13=29 which might be c29t0d1, which doesn't correspond to anything from your iostat listing. Do you have a c29t0d1 device on the system?

JP

[Yogeeraj_1]

iostat iteratively reports I/O statistics for each active disk on the system.


Hence, the information you have posted is for Disk data arranged in a four-column format:

Column Heading Interpretation
device Device name
bps Kilobytes transferred per second
sps Number of seeks per second
msps Milliseconds per average seek

Hope this helps!

Best Regards
Yogeeraj