From: Michael Buesch <fsdeveloper@yahoo.de>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [2.5.70] possible problem with /dev/diskstats
Date: Sun, 1 Jun 2003 21:31:31 +0200 [thread overview]
Message-ID: <200306012131.32006.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <200306011905.h51J57Q03929@owlet.beaverton.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[I think we can take Andrew out of the cc list, because it
seems to be not caused by his patch, then]
On Sunday 01 June 2003 21:05, Rick Lindsley wrote:
> Documentation/iostats.txt says about diskstats:
> [SNIP]
> Field 9 -- # of I/Os currently in progress
> The only field that should go to zero. Incremented as requests are
> given to appropriate request_queue_t and decremented as they
> finish. [SNIP]
>
> But here is a cat /proc/diskstats:
> 3 0 hda 948 317 16216 4294408142 90 333 848 7309 4294967294
> 7309215 4280372198 ~~~~~~~~~~
>
> Yes, I've had a couple of other reports of this. I suspect there is
> a path by which an "I/O" appears to have been completed while none was
> begun. I've only noticed this on my hda drive as well. What I didn't
> notice was exactly when this behavior began, which may have been useful
> in tracking down the problem. You'll notice a couple of other values
> there in the 4.2 billion range that probably suffer from a similar
> (or maybe the same) issue. I haven't seen this on SCSI drives yet,
> just hda drives, which suggests there may be something about that I/O
> path that bears some closer scrutiny.
I've restarted the server and it has an uptime of
21:26:36 up 3:20, 1 user, load average: 0.00, 0.00, 0.00
I've done some disk-io (compiled some software) and the values
now are even lower:
3 0 hda 1623 415 28028 128689845 408 1657 4144 61294 4294967234 11728672 3714354303
3 1 hda1 4 8 1 2
3 2 hda2 1966 28002 2071 4142
3 64 hdb 381 18 3272 124256894 1662 1332 24000 61697 4294967248 11733826 3870100758
Directly after reboot it is:
21:30:55 up 1 min, 1 user, load average: 0.15, 0.08, 0.02
3 0 hda 904 311 15432 4294408137 66 213 564 7358 4294967294 67078 4294856106
3 1 hda1 4 8 0 0
3 2 hda2 1208 15416 282 564
3 64 hdb 45 0 344 4294400418 8 3 88 404 4294967294 72358 4294841430
Where exactly is the code in the kernel, that produces the diskstats file,
so I can try grepping through it?
>
> Rick
- --
Regards Michael Büsch
http://www.8ung.at/tuxsoft
21:23:47 up 2:09, 3 users, load average: 1.01, 1.01, 1.00
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+2lSToxoigfggmSgRAuSgAJ42rV0+KTChl6OzUXf7KftHyi8b/wCfXaaJ
nOQzW3tR2UwVo15DpdRPzUQ=
=nGvx
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-01 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 22:35 [2.5.70] possible problem with /dev/diskstats Michael Buesch
2003-06-01 19:05 ` Rick Lindsley
2003-06-01 19:31 ` Michael Buesch [this message]
2003-06-02 4:23 ` Rick Lindsley
2003-06-02 5:10 ` Maneesh Soni
2003-06-02 14:19 ` Michael Buesch
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=200306012131.32006.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricklind@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.