public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Miquel van Smoorenburg <mikevs@xs4all.net>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: disk statistics issue in 2.6.27
Date: Wed, 22 Oct 2008 19:17:12 +0200	[thread overview]
Message-ID: <20081022171712.GO22217@kernel.dk> (raw)
In-Reply-To: <1224686272.25437.14.camel@n2o.xs4all.nl>

On Wed, Oct 22 2008, Miquel van Smoorenburg wrote:
> On Mon, 2008-10-20 at 19:12 +0200, Jens Axboe wrote:
> > On Sun, Oct 19 2008, Miquel van Smoorenburg wrote:
> > > I just upgraded one of our servers in the nntp cluster to 2.6.27.1 -
> > > most of the others are running 2.6.26.something.
> > > 
> > > I noticed that the "iostat -k -x 2" output does't make any sense.
> > > The number of reads/sec and number of writes/sec are about what I
> > > would expect, and so are the other fields, but rkB/sec and wkB/sec
> > > are  completely off-scale: gigabytes read/written per second.
> >
> > Weird, I cannot reproduce this at all, iostat works fine for me in .26,
> > .27 and current -git as well. So it's just a plain SCSI drive from
> > linux, no software raid or dm?
> 
> It's a 3-disk hardware RAID5 array, Adaptec 2005S, dpt_i2o driver.
> 
> > Are the reported values in iostat any sort of multiple of the real
> > throughtput, or is is just insanely large?
> 
> It looks like it's a multiple, but it appears to vary between 128 and
> 512, and is different for reads and writes, so I do not know what to
> make of it.
> 
> I tried to reproduce it on different systems - on another box with a
> 2010S controller I'm seeing the same thing. But on a different box with
> SATA drives I cannot reproduce the problem.
> 
> Thanks for looking at this. I guess I'll have to start putting debug
> statements in block/gendisk.c to find out what's wrong. I might not have
> time for it until after next week though, but I won't give up :)

It's all really weird, especially if you see it on drivers both using
the SCSI layer. And it's a multiple of the transfer size, then it can't
be something like requeues skewing the count. But do look into it, I'll
do some testing on various drivers tomorrow as well.

-- 
Jens Axboe


  reply	other threads:[~2008-10-22 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19 11:31 disk statistics issue in 2.6.27 Miquel van Smoorenburg
2008-10-20 17:12 ` Jens Axboe
2008-10-22 14:37   ` Miquel van Smoorenburg
2008-10-22 17:17     ` Jens Axboe [this message]
2008-10-23 16:05       ` Miquel van Smoorenburg
2008-10-31 12:47         ` Jens Axboe
2008-11-03 21:39           ` Miquel van Smoorenburg

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=20081022171712.GO22217@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikevs@xs4all.net \
    /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