On Tue, 2006-03-07 at 23:52 -0600, Jonathan Berry wrote:
> >Is anyone else seeing this? I'm assuming that it is not
supposed to
> >do that. Any ideas about how to debug this?
> >
Yes I've experienced the same behaviour a couple times. The most
recent
this afternoon. It took 5 minutes to have the system respond enough so I
could kill it. It swallowed 300MB of my 512MB RAM and was seriously
thrashing my storage.
Well, I didn't mention high CPU usage as I didn't really
notice that.
I also am not really sure exactly what the above means. I did notice
that something locked up my disk really well accessing it for a short
while. The I/O wait cycles tied up the entire CPU, so I wasn't able
to do much to find out what program it was, but it seems likely to
have been beagled.
I had load numbers nearing 9 when I finally got the beagle program
killed.