From: Tejun Heo <tj@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Greg Freemyer <greg.freemyer@gmail.com>,
Yuhong Bao <yuhongbao_386@hotmail.com>,
jeff@garzik.org, ben.collins@ubuntu.com,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: support for drives larger than 2TiB
Date: Sun, 25 Jul 2010 09:49:54 +0200 [thread overview]
Message-ID: <4C4BECA2.3090709@kernel.org> (raw)
In-Reply-To: <20100724232247.GA2129@khazad-dum.debian.net>
Hello,
On 07/25/2010 01:22 AM, Henrique de Moraes Holschuh wrote:
> On Sat, 24 Jul 2010, Greg Freemyer wrote:
>> Secondly, if you look at the table on the right of
>> http://en.wikipedia.org/wiki/Master_boot_record#Disk_partitioning you
>> see that the starting sector of a partition is defined with a 32-bit
>> value.
>>
>> ie. 2TB with 512 byte sectors.
>>
>> The normal solution is to move to a GPT which requires EFI if you want
>> to boot from it.
>
> Can't one have a GPT with a guard boot sector which can read the real
> partition table?
Yeah, parted already does that although there seem to be some bugs and
they sometimes are inconsistent. In principle, BIOSes don't really
care about the partition table (they look at it primarily to figure
out geometry and stuff) and can boot as long as the initial boot
sector is accessible.
> I think Tejun must mean some big problem at the BIOS APIs required for the
> bootloader. Tejun, what exactly croaks at the 2TB boundary (with 512KiB
> sectors)?
The 2TiB limit is coming from BIOS software interrupt for disk access
using 32bit for addressing. If there's 64bit extension to BIOS disk
access, everything should work but still locating boot partition under
2TiB is pretty much required at this point, I think.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-07-25 7:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 9:58 support for drives larger than 2TiB Tejun Heo
2010-07-24 12:21 ` Henrique de Moraes Holschuh
2010-07-24 12:36 ` Alex Buell
2010-07-24 13:49 ` Valdis.Kletnieks
2010-07-24 21:15 ` Alex Buell
2010-07-24 18:40 ` Yuhong Bao
2010-07-24 21:38 ` Greg Freemyer
2010-07-24 23:22 ` Henrique de Moraes Holschuh
2010-07-25 7:49 ` Tejun Heo [this message]
2010-07-25 2:25 ` Yuhong Bao
2010-07-25 8:01 ` Tejun Heo
2010-07-25 8:07 ` H. Peter Anvin
2010-07-25 8:20 ` Tejun Heo
2010-07-25 18:52 ` H. Peter Anvin
2010-07-27 8:41 ` Tejun Heo
2010-07-25 8:26 ` Alex Buell
2010-07-25 18:53 ` H. Peter Anvin
2010-07-24 18:48 ` Yuhong Bao
2010-08-19 13:12 ` Mark Lord
2010-08-23 7:40 ` Yuhong Bao
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=4C4BECA2.3090709@kernel.org \
--to=tj@kernel.org \
--cc=ben.collins@ubuntu.com \
--cc=greg.freemyer@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuhongbao_386@hotmail.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