From: Michael Buesch <fsdeveloper@yahoo.de>
To: maneesh@in.ibm.com
Cc: Rick Lindsley <ricklind@us.ibm.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.70] possible problem with /dev/diskstats
Date: Mon, 2 Jun 2003 16:19:32 +0200 [thread overview]
Message-ID: <200306021619.43005.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <20030602051030.GB1256@in.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 02 June 2003 07:10, Maneesh Soni wrote:
> On Sat, May 31, 2003 at 10:40:21PM +0000, Michael Buesch wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi.
> >
> > I've just played around with my server (that has actualy no load)
> > and I recognized something strange in /dev/diskstats.
> >
> > 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:
> > 1 0 ram0 0 0 0 0 0 0 0 0 0 0 0
> > 1 1 ram1 0 0 0 0 0 0 0 0 0 0 0
> > 1 2 ram2 0 0 0 0 0 0 0 0 0 0 0
> > 1 3 ram3 0 0 0 0 0 0 0 0 0 0 0
> > 1 4 ram4 0 0 0 0 0 0 0 0 0 0 0
> > 1 5 ram5 0 0 0 0 0 0 0 0 0 0 0
> > 1 6 ram6 0 0 0 0 0 0 0 0 0 0 0
> > 1 7 ram7 0 0 0 0 0 0 0 0 0 0 0
> > 1 8 ram8 0 0 0 0 0 0 0 0 0 0 0
> > 1 9 ram9 0 0 0 0 0 0 0 0 0 0 0
> > 1 10 ram10 0 0 0 0 0 0 0 0 0 0 0
> > 1 11 ram11 0 0 0 0 0 0 0 0 0 0 0
> > 1 12 ram12 0 0 0 0 0 0 0 0 0 0 0
> > 1 13 ram13 0 0 0 0 0 0 0 0 0 0 0
> > 1 14 ram14 0 0 0 0 0 0 0 0 0 0 0
> > 1 15 ram15 0 0 0 0 0 0 0 0 0 0 0
>
> Rick,
>
> ramdisk stats are also always zero whether you do any IO or not. Any idea
> where this can be corrected.
Hmm, yes, I've had /var on ram0 in this example, but it doesn't show
any statistics for it.
> Thanks
> Maneesh
- --
Regards Michael Büsch
http://www.8ung.at/tuxsoft
16:17:13 up 20 min, 1 user, load average: 1.00, 0.97, 0.74
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+21z+oxoigfggmSgRAvqPAJ9ZXw2Rrk1FZQovWUu58xQlNEareACeLVoo
ZVw22gyiSz3ehXdtxaK+LlM=
=Rw7M
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-06-02 14:12 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
2003-06-02 4:23 ` Rick Lindsley
2003-06-02 5:10 ` Maneesh Soni
2003-06-02 14:19 ` Michael Buesch [this message]
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=200306021619.43005.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox