From: Andries Brouwer <aebr@win.tue.nl>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: linux-kernel@vger.kernel.org
Subject: Re: bio too big device
Date: Wed, 12 Mar 2003 22:28:46 +0100 [thread overview]
Message-ID: <20030312212846.GA4925@win.tue.nl> (raw)
In-Reply-To: <b4nsh7$eg0$1@penguin.transmeta.com>
On Wed, Mar 12, 2003 at 05:59:03PM +0000, Linus Torvalds wrote:
> >We have seen *zero* drives that do not understand 256 sector commands.
> >Maybe such drives exist, but so far there is zero evidence.
>
> That is definitely not true. We definitely _have_ had drives that
> misconstrue the 256-sector case. It's been a long time, but they
> definitely exist.
I disagree. If you have any proof, please show it.
Let me repeat:
We have seen *zero* drives that do not understand 256 sector commands.
We have seen *one* drive (a six years old Maxtor 7850AV) that could not
sustain heavy load with max # secs set to 256, while it behaved better
with max set to 255.
But we have seen lots of old old drives that show all kinds of errors.
> The right limit for IDE is 255 sectors, and doing 256 sectors WILL fail
> on some setups.
Paul remarked: "So the 255 (or even the old 128) fixes things vs. 256,
but I'd feel better being 100% sure why. Is 255 a "fix" or a perturbation
that happens to paper over something else?"
I think there is no good reason to limit us to 255 sectors.
(And no reason for blacklists either - there is just no good evidence
that something is systematically wrong with 256 sectors for any brand or
model. Things would change if a second Maxtor 7850AV owner could confirm.)
Andries
next prev parent reply other threads:[~2003-03-12 21:18 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 [this message]
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
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=20030312212846.GA4925@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).