Understanding Linux Load Average – Part 1

Originally posted on The Dutch Prutser's Blog:

A frequently asked question in my classroom is “What is the meaning of load average and when is it too high?”. This may sound like an easy question, and I really thought it was, but recently I discovered that things aren’t always that easy as they seem. In this first of a three-part post I will explain what the meaning of Linux load average is and how to diagnose load averages that may seem too high.

Obtaining the current load average is very simple by issuing the uptime command:

1

But what is the meaning of these 3 numbers? Basically load average is the run-queue utilization averaged over the last minute, the last 5 minutes and the last 15 minutes. The run-queue is a list of processes waiting for a resource to become available inside the Linux operating…

View original 1,941 more words

About these ads

About Raheel Syed

Oracle DBA
This entry was posted in Linux and tagged , , , . Bookmark the permalink.

3 Responses to Understanding Linux Load Average – Part 1

  1. Pingback: Ίδρυμα Linux: «Χρησιμοποιείς Linux είτε το ξέρεις, είτε όχι» | TECH . BUZZ . GREECE

  2. Ahmed says:

    Dude have you come across below error on Redhat LINUX…i am having this issue…!!

    Apr 1 07:54:11 enjproddb kernel: EXT3-fs error (device dm-8): ext3_get_inode_loc: unable to read inode block – inode=5522104, block=11042839
    Apr 1 07:54:11 enjproddb kernel: inode_doinit_with_dentry: getxattr returned 5 for dev=dm-8 ino=5522104
    Apr 1 07:54:11 enjproddb kernel: scsi0 (5:3): rejecting I/O to offline device
    Apr 1 07:54:11 enjproddb kernel: EXT3-fs error (device dm-8): ext3_get_inode_loc: unable to read inode block – inode=5522565, block=11042854
    Apr 1 07:54:11 enjproddb kernel: inode_doinit_with_dentry: getxattr returned 5 for dev=dm-8 ino=5522565
    Apr 1 07:54:11 enjproddb kernel: scsi0 (5:3): rejecting I/O to offline device
    Apr 1 07:54:11 enjproddb kernel: EXT3-fs error (device dm-8): ext3_get_inode_loc: unable to read inode block – inode=5522243, block=11042844
    Apr 1 07:54:11 enjproddb kernel: inode_doinit_with_dentry: getxattr returned 5 for dev=dm-8 ino=5522243
    Apr 1 07:54:11 enjproddb kernel: scsi0 (5:3): rejecting I/O to offline device
    Apr 1 07:54:11 enjproddb kernel: EXT3-fs error (device dm-8): ext3_get_inode_loc: unable to read inode block – inode=5522476, block=11042851
    Apr 1 07:54:11 enjproddb kernel: inode_doinit_with_dentry: getxattr returned 5 for dev=dm-8 ino=5522476

    Is this the Kernel issue…??? or Hardware storage issue….or SAS HBA card issue….????

    Regards,

    Ahmed.

  3. Raheel Syed says:

    Mate. No idea :) better check with SA

    Raheel Syed

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s