On Fri, October 25, 2013 1:36 pm, Michael Chesterton wrote: > I know it's resolved, but look at the 6th column in the original post. > 90+% iowait, 90% of the time, the cpu is waiting for IO.
> now what you should do is run the same command when everything is working > normally so you'll know what the output looks like. Then when you have > another problem, you can compare with the normal output. -- the "resolved" problem keeps coming back, under normal situation, I'm ruining load average of .2 then, for maybe 1 to 2 hours high iowait, load average peaks at 130+ aprt from sar and bonnie (haven't installed it yet, wasn't in my repo), what other indicators can I use ? I'm thinking of feeding it into cacti. meanwhile, data centre response has been: 'we can ping it, there is nothing wrong' and 'reboot the server' -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
