mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: jmerkey <jmerkey@utah-nac.org>,
	Bernd Eckenfels <ecki@lina.inka.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Devices/Partitions over 2TB
Date: Wed, 16 Mar 2005 09:06:10 -0500	[thread overview]
Message-ID: <20050316140610.GG17865@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1110975416.1959.21.camel@sisko.sctweedie.blueyonder.co.uk>

On Wed, Mar 16, 2005 at 12:16:57PM +0000, Stephen C. Tweedie wrote:
> For LVM, the lvm2 package contains all the necessary tools.  I know
> Alasdair did some kernel fixes for lvm2 striping on >2TB partitions
> recently, though, so older kernels might not work perfectly if you're
> using stripes.
> 
> To use genuine partitions > 2TB, though, you need alternative
> partitioning; the GPT disk label supports that, and "parted" can create
> and partition such disk labels.  (Note that most x86 BIOSes can't boot
> off them, though, so don't do this on your boot disk!)

Does the BIOS actually support partitions in general?  I thought that
was a problem for the code in the MBR.  As long as your bootcode in the
MBR supports whatever partition scheme you come up with, I can't see how
it should be a problem, but maybe I am missing something.  So what does
GRUB/LILO support?

Len Sorensen

  reply	other threads:[~2005-03-16 14:06 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 [this message]
2005-03-17 13:07 ` Andries Brouwer

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=20050316140610.GG17865@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=ecki@lina.inka.de \
    --cc=jmerkey@utah-nac.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.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

all inboxes | Powered by JetHome®