Red Hat Bugzilla – Bug 137595
iostat information for SAN luns is wrong
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
When comparing the information gathered from /proc/stat and from
/proc/partitions (using iostat) there is a large difference. I've
written a tool that gets this information from both /proc/stat and
/proc/partitions (the way iostat does it) and the information from
/proc/stat conforms with the vmstat info _and_ with what we see on the
So the iostat info is plainly wrong.
The setup is a Linux node connected to a SAN with 2 QLogic 2312 adapters.
I can guide you how to verify this information using dstat with both
/proc/stat and /proc/partitions. (Because the /proc/stat functionality
has currently been commented out in subversion). This is what it looks
like when both are enabled:
[root@node01 san]# /root/dstat -d -D sdb,hires 8
____sdb____ ___hires___|____sdb____ ___hires___
0B 0B: 0B 0B| 0B 0B: 0B 0B
0B 15M: 0B 156M| 0B 32M: 0B 325M
0B 17M: 0B 171M| 0B 29M: 0B 300M
0B 17M: 0B 173M| 0B 28M: 0B 283M
0B 16M: 0B 162M| 0B 28M: 0B 283M
0B 18M: 0B 176M| 0B 28M: 0B 283M
0B 17M: 0B 170M| 0B 29M: 0B 293M
Exiting on user request
The left is /proc/stat, the right is /proc/partitions (iostat formula,
iostat gives exactly the same info) The hires information is actually
the sum for 10 luns that belong to the same filesystem (striped over
the 10 luns).
The code for dstat is open, so you can experiment with it and verify
I consider this bug critical since this means the iostat data cannot
be trusted and when monitoring more 29 luns, /proc/stat is useless.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Let me add that this is Red Hat Advanced Server 3 U3 with kernel
Do you have access the RHEL3 update 4 beta? There's a new version
of the sysstat package (5.0.5) that uses /proc/partitions.
Otherwise, check out:
I only found sysstat-5.0.5-1 and it indeed fixed the problem. Now I
have to look what has changed and fix dstat too.
Thanks for the hint.