From: Andrew Morton <akpm@digeo.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.60 and current bk oops in file_ra_state_init
Date: Thu, 13 Feb 2003 13:13:44 -0800 [thread overview]
Message-ID: <20030213131344.086e154e.akpm@digeo.com> (raw)
In-Reply-To: <20030213120445.A15070@beaverton.ibm.com>
Patrick Mansfield <patmans@us.ibm.com> wrote:
>
> Hi -
>
> Using the scsi-misc-2.5 (2.5.60 plus a few changes), or the current
> bk (as of this morning) I'm hitting an oops in file_ra_state_init.
Oh lovely. Looks like the blockdev/gendisk refcounting has gone wrong and a
request queue was freed under your app's feet.
> I was trying to run a bunch of raw IO's (/dev/raw/rawN) at once to several
> (well 25) disks, trying to maximize IO's/second by repeatedly reading the
> same block of a disk, and got the following oops. I hit this both on a
> netfinity and NUMAQ box.
Was this test frequently opening and closing device nodes, or does it just
open them once and hold them?
Can you please prepare a testcase which I can use to reproduce this?
Be aware that there are some fairly significant problems with direct I/O at
present - direct-io can cause multiple outstanding requests against the same
sector, and that makes the IO scheduler keel over. But it would be strange
for that to be related to this failure.
BTW, you don't need to use the raw driver any more. Just open /dev/sda1 with
O_DIRECT. In fact, I'd be interested in seeing if this change makes the oops
go away.
Thanks.
next prev parent reply other threads:[~2003-02-13 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:04 Patrick Mansfield
2003-02-13 21:13 ` Andrew Morton [this message]
2003-02-13 22:29 ` Patrick Mansfield
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=20030213131344.086e154e.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patmans@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
all inboxes | Powered by JetHome®