public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bio too big device
Date: Fri, 14 Mar 2003 06:19:18 -0500	[thread overview]
Message-ID: <3E71BAB6.AFB608BC@yahoo.com> (raw)
In-Reply-To: 20030312212846.GA4925@win.tue.nl

Andries Brouwer wrote:

> 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.

[...] 

> 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?"

As luck would have it, I kept that drive around, thinking it might be
interesting to have around if the above "why" part got revisited
someday.

> 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.)

Perhaps I can also act as the second owner in this case.  :-) The drive is 
currently in an old 16MB P133 on a PIIX3, so after tripping over this 
thread, I did some testing to 1st see if I could still re-create any 
problems in this different box.  Of note, 2.4.21pre5 reports:

hda: 1667232 sectors (854 MB) w/64KiB Cache, CHS=1654/16/63, BUG DMA OFF
                                        -------------------->^^^
which I haven't looked into yet. Anyway, I tweaked pre5 to re-allow 256
and then let it do two 2.5.64 compiles at the same time (in 16MB, this
takes a while) and nothing broke.  Thinking that the original problem was 
in an even older VLB box, I disabled DMA and did the same test. Still no
breakage.

What does this mean?  I'm not sure :)  Maybe this simple test isn't as
harsh as the prior one from several years ago.   Realistically, there 
are a fair number of changes that also may have a role: e.g.  ide driver, 
gcc, gas, kernel, CPU, mainboard, ide controller, PSU, cables, and so on 
all have changed.  It looks like I would need to jump back into the past 
and test on the exact same system and then progressively rule out some 
of these variables.
 
Paul.


  reply	other threads:[~2003-03-14 11:16 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 [this message]
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=3E71BAB6.AFB608BC@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=aebr@win.tue.nl \
    --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