-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Tuesday 2007-04-17 at 11:15 +0200, Clayton wrote:

> I traced the problem.... a failing IDE hard drive.  Here's a little
> info to close off this thread.
> 
> From the look of it, it was coincidental that Ruby was involved.  Ruby
> seemed to be involved because whatever script it was handling was
> attempting read or write into the bad area.  The result... the system
> paused briefly while it tried to sort out the read/write error.

Makes sense... after we know it :-)

There is an applet that might have helped. You know those kinds of applets 
that show a cpu usage graph? But there is one type of "busy" that doesn't 
usually show, and it is the percent of time the cpu is waiting for I/O. 
Typicals are "user, system, nice, idle", but IOwait is usually neglected. 
The gnome cpu monitor does show it, in black over black, and I always 
change it to some dark color that I can see: thus I know when my system 
becomes unresponsive but cpu is low that disk usage is high; ie, that the 
cpu is waiting for the disk.

In your case it could have shown something.

- -- 
Cheers,
       Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFGJJ4xtTMYHG2NR9URAoBsAJ9ThTVOMWZex+7sL3jZqXIOalXkhwCeJVur
StTRvg9SyruCpRM2Dxift5I=
=eWXy
-----END PGP SIGNATURE-----

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to