All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Andre Hedrick <andre@linux-ide.org>,
	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 16:51:05 +0100	[thread overview]
Message-ID: <20030312155105.GJ834@suse.de> (raw)
In-Reply-To: <20030312154440.GA4868@win.tue.nl>

On Wed, Mar 12 2003, Andries Brouwer wrote:
> On Wed, Mar 12, 2003 at 11:14:14AM +0100, Jens Axboe wrote:
> 
> > So I still think it's much better stick with the safe choice. Why do you
> > think it's only one drive that has this bug? It basically boils down to
> > whether That Other OS uses 256 sector commands or not. If it doesn't, I
> > wouldn't trust the drives one bit.
> 
> I am not quite sure I understand your reasoning.
> We have seen *zero* drives that do not understand 256 sector commands.
> Maybe such drives exist, but so far there is zero evidence.

Have you read the thread? You are obviously mistaken.

-- 
Jens Axboe


  reply	other threads:[~2003-03-12 15:41 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 [this message]
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=20030312155105.GJ834@suse.de \
    --to=axboe@suse.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.