linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mudama, Eric" <eric_mudama@maxtor.com>
To: "'Anders Larsson'" <anders@dio.jll.se>, linux-kernel@vger.kernel.org
Subject: RE: bio too big device
Date: Wed, 16 Apr 2003 12:43:06 -0600	[thread overview]
Message-ID: <785F348679A4D5119A0C009027DE33C102E0D134@mcoexc04.mlm.maxtor.com> (raw)



> -----Original Message-----
> From: Anders Larsson [mailto:anders@dio.jll.se]
> Sent: Wednesday, April 16, 2003 12:32 PM
>
> hdg: WDC WD1200JB-00DUA0, ATA DISK drive  
> hdg: host protected area => 1
> hdg: 234441648 sectors (120034 MB) w/8192KiB Cache, 
> CHS=14593/255/63,       
> UDMA(100)
> 
> hdh: WDC WD1200JB-75CRA0, ATA DISK drive
> hdh: host protected area => 1
> hdh: setmax LBA 234441648, native  234375000
> hdh: 234375000 sectors (120000 MB) w/8192KiB Cache, 
> CHS=232514/16/63,       
> UDMA(100)


On hdh, it appears you're setting the max lba > the native size.  Maybe this
is the problem.

For RAID on two drives, I would imagine your RAID size would need to be the
size of the smaller device, not the larger device.  (Note that they aren't
identical).

Not sure if the two different CHS translation modes on each drive is
important or not (probably not), that legacy bios stuff is something that
has always confused me...

--eric

             reply	other threads:[~2003-04-16 18:31 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 18:43 Mudama, Eric [this message]
     [not found] <20030416172122.M65357@gw>
     [not found] ` <20030416181944.M32238@gw>
2003-04-16 18:32   ` bio too big device Anders Larsson
2003-04-17 13:36     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:19 Manfred Spraul
2003-03-12 21:40 ` Alan Cox
2003-03-12  2:55 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
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

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=785F348679A4D5119A0C009027DE33C102E0D134@mcoexc04.mlm.maxtor.com \
    --to=eric_mudama@maxtor.com \
    --cc=anders@dio.jll.se \
    --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;
as well as URLs for NNTP newsgroup(s).