From: David Mansfield <lkml@dm.cobite.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] raw over raid5: BUG at drivers/block/ll_rw_blk.c:1967
Date: Mon, 14 Oct 2002 17:57:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0210141755340.2876-100000@admin> (raw)
In-Reply-To: <3DAB2DD9.B78639C5@digeo.com>
On Mon, 14 Oct 2002, Andrew Morton wrote:
> David Mansfield wrote:
> >
> > Hi everyone,
> >
> > I haven't been able to run raw over raid5 since 2.5.30 or so, but every
> > time I'm about to report it, a new kernel comes out and the problem
> > changes completely :-( Now I'm finally going to start getting out the info
> > it the hopes someone can fix it. The oops was triggered by attempting to
> > read from /dev/raw/raw1 (bound to /dev/md0) using dd. System info
> > follows oops:
> >
> > ------------[ cut here ]------------
> > kernel BUG at drivers/block/ll_rw_blk.c:1967!
>
> I don't think you told us the kernel version?
Arrgh. It was 2.5.42 vanilla.
> There have been recent fixes wrt sizing of the BIOs which the
> direct-io layer sends down. So please make sure that you're
> testing Linus's current -bk, or 2.5.42 plus
>
> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.42/2.5.42-mm2/broken-out/dio-bio-add-fix-1.patch
I've applied this patch and retested. I was able to run dd once this
time, hit ctrl-c, all ok. But I hit up-arrow and re-did it and it gave
the same oops. I'm going to try with the full (latest) mm patch.
> Either that, or raid5 is bust ;)
>
I guess so.
David
--
/==============================\
| David Mansfield |
| lkml@dm.cobite.com |
\==============================/
next prev parent reply other threads:[~2002-10-14 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 20:36 [BUG] raw over raid5: BUG at drivers/block/ll_rw_blk.c:1967 David Mansfield
2002-10-14 20:49 ` Andrew Morton
2002-10-14 21:57 ` David Mansfield [this message]
2002-10-14 22:18 ` David Mansfield
2002-10-15 6:41 ` Neil Brown
2002-11-05 23:43 ` Neil Brown
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=Pine.LNX.4.44.0210141755340.2876-100000@admin \
--to=lkml@dm.cobite.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.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.