From: Rick Lindsley <ricklind@us.ibm.com>
To: Jean-Luc Fontaine <jfontain@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.1: erroneous statistics in /proc/diskstats?
Date: Mon, 19 Jan 2004 02:58:02 -0800 [thread overview]
Message-ID: <200401191058.i0JAw2S14446@owlet.beaverton.ibm.com> (raw)
In-Reply-To: Your message of "Sun, 18 Jan 2004 18:11:55 +0100." <400ABE5B.6090701@free.fr>
I would like to make sure /proc/diskstats is reliable or if I am totally
misunderstanding the significance of the milliseconds spent reading or
writing figures.
So far as I know, they are reliable but there always could be a bug.
Note that it is legitimate for field 8 to be greater than the time
elapsed, since it is the *total* time spent in *all* writes. If two write
requests were issued simultaneously and each fulfilled simultaneously,
taking exactly 10ms, you'd account for 20ms of "write I/O" even though
only 10ms of time has passed.
So, a few more details ...
How big was it?
How did you copy it (what command)?
Were you going through a file system or direct to disk?
One thing I notice is that your hdc shows 100+ "io's in progress" both
at start and completion. It may be as simple as that counter is off.
If there are IO's in progress when you start and they haven't finished
by the time you end, then they will certainly add about 6 seconds of
"write time" for each outstanding, apparently unfulfilled request.
This alone could account for your extra time. Any theories on why that
number is so large for hdc but quite small for hdb?
Rick
next prev parent reply other threads:[~2004-01-19 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 17:11 Jean-Luc Fontaine
2004-01-19 10:58 ` Rick Lindsley [this message]
2004-01-19 13:13 ` Jean-Luc Fontaine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401191058.i0JAw2S14446@owlet.beaverton.ibm.com \
--to=ricklind@us.ibm.com \
--cc=jfontain@free.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®