From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: 3TB disk hassles
Date: Sat, 18 Dec 2004 03:08:42 +0000 (UTC) [thread overview]
Message-ID: <cq06vq$1t2$1@terminus.zytor.com> (raw)
In-Reply-To: 20041218001254.GA8886@pclin040.win.tue.nl
Followup to: <20041218001254.GA8886@pclin040.win.tue.nl>
By author: Andries Brouwer <aebr@win.tue.nl>
In newsgroup: linux.dev.kernel
>
> Yes, indeed.
>
> One can use a standard DOS-type partition table, and pick a new type -
> I reserved 88 for this purpose today - where type 88 indicates a
> plaintext partition table found elsewhere on the disk.
> Where is elsewhere? In the starting sector of the type 88 partition
> (that can have length 1).
> This allows one to have the initial part of the disk (at most 2 TB)
> partitioned in old-fashioned manner.
>
> The plaintext partition table is just a table with lines
> <start> <size>
> that one can edit with emacs or vi.
>
> There is magic to recognize it, namely the line
> "# Plaintext partition table"
> and magic to indicate the end of the table, namely "# end".
>
> That is all. If anybody wants it I can send the trivial code.
> (Am using it now, but unfortunately I do not have 3 TB disks.)
>
First, what's wrong with the GUID partition table format? Let's stick
to standards as long as they work; especially for things that
potentially affect multiple operating systems.
Second, several problems with this. Sector 0 is the boot sector, so
using it is a really bad choice. (I'd reserve several sector for
master boot code.) In fact, rather than having a separate partition,
why don't we just specify that a sector starting with "# Plaintext partition
table" has to start within the first 64 sectors of the disk (it's
common for DOS partition tables to have the first partition start at
offset 63.)
Third, it ought to be possible to put more information than this,
e.g. for raid detect.
-hpa
next prev parent reply other threads:[~2004-12-18 3:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 14:52 3TB disk hassles Neil Conway
2004-12-16 15:33 ` Michelle Konzack
2004-12-16 15:37 ` Mark Watts
2004-12-16 15:38 ` Hans Kristian Rosbach
2004-12-16 16:44 ` Neil Conway
2004-12-16 17:15 ` Tomas Carnecky
2004-12-16 17:38 ` Neil Conway
2004-12-16 18:05 ` Tomas Carnecky
2005-02-05 1:47 ` Neil Conway
2004-12-16 17:40 ` Tomas Carnecky
2004-12-16 15:52 ` Michelle Konzack
2004-12-16 16:03 ` Jan Engelhardt
2004-12-16 16:00 ` Alan Cox
2004-12-18 0:12 ` Andries Brouwer
2004-12-18 3:08 ` H. Peter Anvin [this message]
2004-12-18 12:15 ` Andries Brouwer
2004-12-18 23:32 ` H. Peter Anvin
2005-01-03 17:13 ` Jeff V. Merkey
2005-01-03 17:32 ` Jeff V. Merkey
2005-01-03 18:11 ` linux-os
2004-12-16 17:10 ` Michelle Konzack
2004-12-16 19:52 ` Adam Heath
2004-12-16 23:28 ` Pedro Venda (SYSADM)
2005-02-05 1:51 ` Neil Conway
2004-12-16 22:21 Rico Tudor
[not found] <fa.fng0mbi.10jm21g@ifi.uio.no>
[not found] ` <fa.ls0rpqi.104a23q@ifi.uio.no>
2005-02-05 2:58 ` Bodo Eggert
2005-02-05 11:14 ` Neil Conway
2005-02-06 10:59 Neil Conway
2005-02-06 19:01 ` Bodo Eggert
2005-02-08 23:33 ` H. Peter Anvin
[not found] <linux.kernel.20041216145229.29167.qmail@web26502.mail.ukl.yahoo.com>
2005-02-10 0:06 ` Jan Lindheim
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='cq06vq$1t2$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--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).