public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Andre Hedrick <andre@linux-ide.org>
Cc: scott thomason <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:47:10 +0100	[thread overview]
Message-ID: <20030312084710.GA4816@win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10303112100270.391-100000@master.linux-ide.org>

> On Tue, 11 Mar 2003, scott thomason 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)

On Tue, Mar 11, 2003 at 09:01:25PM -0800, Andre Hedrick wrote:

> That has to be a BIO bug or IDE setup bug.
> 
> 256 sectors is legal and correct for 28-bit addressing.

Yes, it is. However, Paul Gortmaker reported on his old 700MB
Maxtor 7850 AV that would give errors with 256-sector requests
and work well with 255-sector requests. In a later post he
added that one has to work hard to evoke this error - usually
256-sector requests are fine, but after torturing the disk with
an hour of simultaneous untar and make, an error occurred.

Maybe that is the only disk that gives problems.

Jens replied:

= The 256 is _not_ a bug in the driver, it's more likely a bug in your
= drive. 256 is a perfectly legal transfer size. That said, maybe it is
= a good idea to leave it at 255 just for safety

So that is how this length was limited.

In short: 256 is legal, has always been legal, nothing wrong with it.
But at least one old disk has been discovered that was happier with 255.

Andries


  reply	other threads:[~2003-03-12  8:36 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
2003-03-12  5:01 ` Andre Hedrick
2003-03-12  8:47   ` Andries Brouwer [this message]
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=20030312084710.GA4816@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --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