[lkml]   [2003]   [Jan]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BUG] BUG_ON in I/O scheduler, bugme # 288
Dave Olien <> 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:

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:

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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.058 / U:1.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site