public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: scott-kernel@thomasons.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bio too big device
Date: Wed, 12 Mar 2003 09:30:47 +0100	[thread overview]
Message-ID: <20030312083047.GH811@suse.de> (raw)
In-Reply-To: <15982.43897.703221.456961@notabene.cse.unsw.edu.au>

On Wed, Mar 12 2003, Neil Brown wrote:
> On Tuesday March 11, scott-kernel@thomasons.org wrote:
> > I frequently receive this message in my syslog, apparently 
> > whenever there are periods of significant write activity:
> > 
> >     bio too big device ide0(3,7) (256 > 255)
> >     bio too big device ide1(22,6) (256 > 255)
> > 
> > It's worth noting that on this system I have had ongoing trouble 
> > with system stability during write activity as well, using a 
> > wide variety of 2.5.x kernels, even though at the time of this 
> > symptom things are apparently running fine.
> > 
> > Filesystems are all ext3 on top soft raid0 devices. This happens 
> > to be 2.5.64, but it has been happening for at least the last 
> > 5-6 versions.
> > 
> > Ideas? Any further debugging output I can provide?
> 
> 
> raid0 doesn't really work well in 2.5 yet.... as you have noticed.
> 
> We really need to grab the bio splitting code out of md/dm.c and use
> it to split bios that are too big or that cross device boundaries.
> 
> any volunteers??

I can give it a shot

-- 
Jens Axboe


  parent reply	other threads:[~2003-03-12  8:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  2:55 bio too big device scott thomason
2003-03-12  3:17 ` scott thomason
2003-03-12  8:18   ` Jens Axboe
2003-03-12  3:37 ` Neil Brown
2003-03-12  3:49   ` scott thomason
2003-03-12  8:30   ` Jens Axboe [this message]
2003-03-12  5:01 ` Andre Hedrick
2003-03-12  8:47   ` Andries Brouwer
2003-03-12  8:59     ` Andre Hedrick
2003-03-12  8:51   ` Jens Axboe
2003-03-12  9:01     ` Andre Hedrick
2003-03-12  9:09       ` Jens Axboe
2003-03-12 10:07         ` Andre Hedrick
2003-03-12 10:14           ` Jens Axboe
2003-03-12 15:44             ` Andries Brouwer
2003-03-12 15:51               ` Jens Axboe
2003-03-12 16:02                 ` Andries Brouwer
2003-03-12 16:06                   ` Jens Axboe
2003-03-12 16:14                 ` John Bradford
2003-03-12 17:59               ` Linus Torvalds
2003-03-12 19:05                 ` John Bradford
2003-03-12 19:14                   ` Linus Torvalds
2003-03-12 22:20                     ` John Bradford
2003-03-12 21:28                 ` Andries Brouwer
2003-03-14 11:19                   ` Paul Gortmaker
2003-03-12 21:45                 ` Alan Cox
2003-03-12 14:54           ` scott thomason
2003-03-12 14:58             ` Jens Axboe
2003-03-12 17:09             ` Alan Cox
2003-03-12 16:14         ` Alan Cox
2003-03-12 15:11           ` Jens Axboe
2003-03-12 17:12             ` Alan Cox
2003-03-12 16:06               ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:19 Manfred Spraul
2003-03-12 21:40 ` Alan Cox
     [not found] <20030416172122.M65357@gw>
     [not found] ` <20030416181944.M32238@gw>
2003-04-16 18:32   ` Anders Larsson
2003-04-17 13:36     ` Alan Cox
2003-04-16 18:43 Mudama, Eric

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=20030312083047.GH811@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=scott-kernel@thomasons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox