From: Helge Hafting <helgehaf@aitel.hist.no>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5.40: raid0_make_request bug and bad: scheduling while atomic!
Date: Sun, 06 Oct 2002 13:20:33 +0200 [thread overview]
Message-ID: <3DA01C81.D2BDD8C7@aitel.hist.no> (raw)
In-Reply-To: <anf7nq$qp2$1@ncc1701.cistron.net>
Miquel van Smoorenburg wrote:
>
> I'm trying to test 2.5.40 on a NNTP peering server that pumps
> hundreds of gigs per day over the network. Interested to see
> if I can increase that with 2.5 ;)
>
> Unfortunately my history databases etc are on RAID0:
>
> raid0_make_request bug: can't convert block across chunks or bigger than 32k 8682080 24
> raid0_make_request bug: can't convert block across chunks or bigger than 32k 8679792 24
>
> This appears to be a known problem, but I couldn't find a pointer
> to a solution anywhere. Scared, I ran fsck -f /dev/md0,
> saw no errors, and booted back to 2.4.19
The workaround is to force BIO's to be no bigger than a page.
That limits performance, but it should still be somewhat better
than the pre-bio times.
This used to be fixable in mpage.c, where a comment
explained what to to in precense of "braindead drivers"
But mpage.c changed sometime between 2.5.36 and 2.5.39.
Now the new include/linux/bio.h has the following:
#define BIO_MAX_PAGES (256)
I tried substituting (1) for (256), but it didn't help.
So I don't mount raid-0 right now.
Helge Hafting
next prev parent reply other threads:[~2002-10-06 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 16:43 Miquel van Smoorenburg
2002-10-06 11:20 ` Helge Hafting [this message]
2002-10-06 12:24 ` Anton Blanchard
2002-10-09 21:47 ` 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=3DA01C81.D2BDD8C7@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=neilb@cse.unsw.edu.au \
/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®