Bug 137414 - Error in vmstat manpage (bi vs. bo column)
Error in vmstat manpage (bi vs. bo column)
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: procps (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karel Zak
Brian Brock
Depends On:
Blocks: 132991
  Show dependency treegraph
Reported: 2004-10-28 08:30 EDT by Michael Paesold
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-19 23:25:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Paesold 2004-10-28 08:30:05 EDT
From Bugzilla Helper:
User-Agent: Opera/7.54 (Windows NT 5.1; U)  [en]

Description of problem:
The manpage for vmstat gets the field description of "bi" and "bo" 
wrong, here it says:

bi: Blocks sent to a block device (blocks/s).
bo: Blocks received from a block device (blocks/s).

But it should be the other way round, really:
bi = blocks in (from CPU perspective)
bo = blocks out (from CPU perspective)

Test youself, that is what vmstat really displays:
bi: Blocks received from a block device (blocks/s).
bo: Blocks sent to a block device (blocks/s).

This seems to be wrong in every release of RedHat linux we have.
It is correct on some other unices.

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

How reproducible:

Steps to Reproduce:
Look at the manpage for vmstat and look at the FIELDS description, 
specifically io -- bi and bo;
then test yourself on an otherwise idle system:
dd if=/dev/zero of=/tmp/testfile bs=1024 count=200000 & vmstat 1 10

You will clearly see, that the manual page is wrong.
Comment 1 Karel Zak 2004-12-07 07:30:24 EST
It will be fixed in RHEL-3-U5. 
Comment 2 Dennis Gregorovic 2005-05-19 23:25:49 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.