From: Andrew Morton <akpm@digeo.com>
To: Dave Olien <dmo@osdl.org>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org, markw@osdl.org,
cliffw@osdl.org, maryedie@osdl.org, jenny@osdl.org
Subject: Re: [BUG] BUG_ON in I/O scheduler, bugme # 288
Date: Thu, 23 Jan 2003 14:38:24 -0800 [thread overview]
Message-ID: <20030123143824.4aae1efd.akpm@digeo.com> (raw)
In-Reply-To: <20030123135448.A8801@acpi.pdx.osdl.net>
Dave Olien <dmo@osdl.org> wrote:
>
>
> Jens, Andrew
>
> The group here doing dbt2 workload measurements have hit a couple of
> problems APPARENTLY in the block I/O scheduler when doing write-intensive
> raw disk I/O through a DAC960 extremeraid 2000 controller.
> This wasn't a problem in 2.5.49. It has appeared since then.
>
> I've filed a bug on the OSDL bugme database. You can read it at:
>
> http://bugme.osdl.org/show_bug.cgi?id=288
The title is "2.5.59 and 2.5.50-mm2". I assume it should be 2.5.59-mm2??
> I've also put a more complete report in my web site:
>
> http://www.osdl.org/archive/dmo/deadline_bugon.
oooh, goody. A new stresstest tool.
> Begin with the README file.
>
> For same reason, the README file isn't appearing on my web page.
> I'll look into that. In the mean time, I've included the contests
> of the README file below.
>
> I'm about to try reproducing the problem on a smaller hardware
> configuration. Then, I'll test whether the same problem occurs with
> read intensive I/O.
OK, thanks.
The important thing about direct-io is that it will frequently cause multiple
I/Os to be in flight against the same disk sector. That will never happen
with regular I/O because the pagecache acts as a synchronisation point.
Probably, this has tickled a bug in the I/O scheduler. Possibly in
direct-io, too - that code's fairly fresh, and quite complex.
next prev parent reply other threads:[~2003-01-23 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 21:54 [BUG] BUG_ON in I/O scheduler, bugme # 288 Dave Olien
2003-01-23 22:38 ` Andrew Morton [this message]
2003-01-23 22:34 ` Dave Olien
2003-01-24 7:50 ` Jens Axboe
2003-01-24 15:47 ` Dave Olien
2003-01-24 1:38 ` Nick Piggin
2003-01-24 2:00 ` Andrew Morton
2003-01-24 2:20 ` Nick Piggin
2003-01-24 7:50 ` Jens Axboe
2003-01-24 15:53 ` Dave Olien
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=20030123143824.4aae1efd.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=axboe@suse.de \
--cc=cliffw@osdl.org \
--cc=dmo@osdl.org \
--cc=jenny@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.org \
--cc=maryedie@osdl.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 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.