Bug 1335119

Description of problem:

Same issue as described in URL below.  No answer given to the actual question of the tens of thousands.  They describe as "counters somewhere have overflown" but no fix or instructions shown for how to deal with that type of situation.

https://github.com/sysstat/sysstat/issues/8

Version-Release number of selected component (if applicable):

sysstat-9.0.4-27.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Run CPU-intensive jobs (in our case oracle)
2. Run pidstat for a few hours
3. Reports have occurrences of impossibly-high resources

Actual results:

Example command:

for i in `seq 1 24`; do
  /usr/bin/pidstat -duhIl 30 118 >> $_filename
done

Report output:

1462942863     32714 4847.07 1792.37    0.00 1678.60     0  23596.53      0.00      0.00  oraclepldsc (LOCAL=NO)

Expected results:

System has only 4x CPUs, so I would expect 6th column to be max 400%, but since we have -I option I would not expect more than 100%.  This is not explained in the FAQ section 4.4.  We are also dividing by total # CPUs with the -I option.

Additional info:

This happens every time we use pidstat.