From: Andries Brouwer <aebr@win.tue.nl>
To: Berkley Shands <berkley@cs.wustl.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Devices/Partitions over 2TB
Date: Thu, 17 Mar 2005 14:07:14 +0100 [thread overview]
Message-ID: <20050317130714.GA5439@pclin040.win.tue.nl> (raw)
In-Reply-To: <200503141644.j2EGiVh0000022634@mudpuddle.cs.wustl.edu>
On Mon, Mar 14, 2005 at 10:44:31AM -0600, Berkley Shands wrote:
> With a Broadcom BC4852 and suitable Sata drives, it is easy to create
> functional devices with well in excess of 2TB raw space. This presents a severe
> problem to partitioning tools, such as fdisk/cfdisk and the like as the
> kernel partition structure has a 32 bit integer max for sector counts. Since
> the read_int() function combined with cround() overflows, ...
You should not read fdisk source but think about the DOS-type partition table.
An entry in such a table describes partition start and end in CHS terms
using 24 bits for start and end, and describes partition start and size
in LBA terms using 32 bits for start and size. If you use sectors of size
512, that limits the use of DOS-type partition tables to disks of at most
2^41 bytes, that is, 2 TiB.
What to do afterwards? Last year I made a hack, reserving type 88 hex for
a Linux plaintext partition table. You must be able to find the kernel patch
somewhere on Google, otherwise ask. No fdisk required, the partition table
is just plaintext that you edit using emacs or vi.
The idea here is to use an ordinary DOS-type partition table for the start
of the disk, and let the type 88 partition describe the rest.
There is also the EFI/GPT disk descriptor that is common on IA64, but not much
used elsewhere. Maybe parted supports it.
Andries
prev parent reply other threads:[~2005-03-17 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 16:44 Berkley Shands
2005-03-14 21:23 ` Miquel van Smoorenburg
2005-03-14 21:35 ` Randy.Dunlap
2005-03-14 23:58 ` jmerkey
2005-03-15 4:47 ` Bernd Eckenfels
2005-03-15 4:54 ` jmerkey
2005-03-16 12:16 ` Stephen C. Tweedie
2005-03-16 14:06 ` Lennart Sorensen
2005-03-17 13:07 ` Andries Brouwer [this message]
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=20050317130714.GA5439@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=berkley@cs.wustl.edu \
--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
all inboxes | Powered by JetHome®