From: Andries.Brouwer@cwi.nl
To: ben@xmission.com, chris@void.printf.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bigggg Maxtor drives (fwd)
Date: Thu, 10 Jan 2002 10:00:14 GMT [thread overview]
Message-ID: <UTC200201101000.KAA311551.aeb@cwi.nl> (raw)
On Thu, Jan 10, 2002 at 04:03:09AM +0000, Chris Ball wrote:
> On Wed, Jan 09, 2002 at 08:14:32PM -0700, Benjamin S Carrell wrote:
> > I would think that you lose that space to formatting
>
> Is this perhaps Maxtor providing their own 'non-standard'[1] definition
> of gigabyte, rather than a technical issue?
>
> [1]: (viz. 'wrong')
No, *all* disk manufacturers *always* use decimal, correctly following
the standard. And it has been like this for many years.
No, this is an entirely different phenomenenon.
In the Large Disk Howto you can read in
http://www.win.tue.nl/~aeb/linux/Large-Disk-4.html#ss4.2
about IDE limits:
ATA Specification (for IDE disks) - the 137 GB limit
At most 65536 cylinders (numbered 0-65535), 16 heads (numbered 0-15),
255 sectors/track (numbered 1-255), for a maximum total capacity of
267386880 sectors (of 512 bytes each), that is, 136902082560 bytes
(137 GB). This is not yet a problem (in 1999), but will be a few
years from now.
And indeed, in 2001 the 137 GB limit was crossed.
In order to make addressing of larger disks possible, a new addressing
mode was introduced (in the ATA6 draft, rev 0b), that uses 48-bit
addressing (instead of 28-bit). Thus, the new limit is roughly
a million times larger.
Thus, we need new code that implements the new addressing.
Since one only hears positive reports on Andre's patch, probably
we should take all of it, but the code for 48-bit addressing
is a small fragment that could also easily be separated out.
Andries
next reply other threads:[~2002-01-10 10:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 10:00 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-10 1:46 Bigggg Maxtor drives (fwd) Andre Hedrick
2002-01-10 3:14 ` Benjamin S Carrell
2002-01-10 4:03 ` Chris Ball
2002-01-10 4:31 ` Jim Crilly
2002-01-10 12:11 ` Rik van Riel
2002-01-10 12:15 ` Jens Axboe
2002-01-10 13:22 ` Marcel J.E. Mol
2002-01-10 14:56 ` Hans Reiser
2002-01-10 15:04 ` Jens Axboe
2002-01-10 12:23 ` Lionel Bouton
2002-01-10 12:40 ` Alan Cox
2002-01-10 12:45 ` David Weinehall
2002-01-10 13:47 ` Alan Cox
2002-01-10 18:59 ` Aaron Blew
2002-01-10 19:14 ` Jens Axboe
2002-01-10 19:14 ` Ricky Beam
2002-01-10 19:59 ` Alan Cox
2002-01-10 19:08 ` Ricky Beam
2002-01-10 4:59 ` Andre Hedrick
2002-01-10 9:50 ` Henning P. Schmiedehausen
2002-01-11 21:13 ` Rogier Wolff
2002-01-12 9:14 ` Andre Hedrick
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=UTC200201101000.KAA311551.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=ben@xmission.com \
--cc=chris@void.printf.net \
--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