From: scott thomason <scott-kernel@thomasons.org>
To: Andre Hedrick <andre@linux-ide.org>,
axboe@suse.de, Andries Brouwer <aebr@win.tue.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bio too big device
Date: Wed, 12 Mar 2003 08:54:17 -0600 [thread overview]
Message-ID: <200303120854.17410.scott-kernel@thomasons.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10303120205250.391-100000@master.linux-ide.org>
Just so everyone knows...these aren't ancient drives I'm talking
about. One is a 30GB Maxtor 5T030H3, less than two years old
IIRC, and the other is a 30GB IBM-DTLA-307030 purchased about
six months ago.
---scott
On Wednesday 12 March 2003 04:07 am, Andre Hedrick wrote:
> No that is wrong to force all other drives to under perform
> because on one. If you are going to impose 255 then pushi it
> back to 128 were it is a single scatter list. This issue has
> bugged me for years and now that we know the exact model we
> apply an exception rule to it.
>
> This is one silly bug that I have heard about.
>
> Cheers,
>
> On Wed, 12 Mar 2003, Jens Axboe wrote:
> > On Wed, Mar 12 2003, Andre Hedrick wrote:
> > > So lets dirty list the one drive by Paul G. and be done.
> > > Can we do that?
> >
> > Who cares, really? There's not much point in doing it, we're
> > talking 248 vs 256 sectors in reality. I think it's a _bad_
> > idea, lets just keep it at 255 and avoid silly drive bugs
> > there.
> >
> > --
> > Jens Axboe
>
> Andre Hedrick
> LAD Storage Consulting Group
next prev parent reply other threads:[~2003-03-12 14:43 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
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 [this message]
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=200303120854.17410.scott-kernel@thomasons.org \
--to=scott-kernel@thomasons.org \
--cc=aebr@win.tue.nl \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox