Excessive processor usage

[Ben Scott]

On 8/6/07, Sean <tech.junk at verizon.net> wrote:
> I am beginning to think it is my drive as the problem, it
> seems to be writing a great deal when I see the problem.
> Time for backups!

  No, the time for backups is *before* you start having trouble.... ;-)

  In my experience, excessive CPU usage usually (*usually*) isn't
associated with a failing disk.  If the disk is failing, the system
will be spending lots of time retrying disk I/O (or resetting the
bus/controller/etc), and thus the CPU will be idle.  Usually.

  At the same time, a busy process that uses both CPU and disk will
cause the behavior you describe.

  It could also be a busy process using memory, causing the system to
hit the swap file, and also to tie up the CPU with memory management.

  Another possibility: Check to see what syslog is doing.  If
something is flooding syslog with entries which syslogd is trying to
write to disk, that can cause the behavior you are describing.  One
thing I find helpful is to put a *.* entry in /etc/syslog.conf with a
target of /dev/tty12; that will have syslogd write everything to
Virtual Console 12.  Then I can hit [CTRL]+[ALT]+[F12] to see what's
being logged in real-time.

-- Ben