From: Mark Watts <m.watts@eris.qinetiq.com>
To: linux-kernel@vger.kernel.org
Cc: Neil Conway <nconway_kernel@yahoo.co.uk>
Subject: Re: 3TB disk hassles
Date: Thu, 16 Dec 2004 15:37:02 +0000 [thread overview]
Message-ID: <200412161537.02804.m.watts@eris.qinetiq.com> (raw)
In-Reply-To: <20041216145229.29167.qmail@web26502.mail.ukl.yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Howdy...
>
> After much banging of heads on walls, I am throwing in the towel and
> asking the experts ;-) ... To cut a long story short:
>
> Is it possible to make a 3TB disk work properly in Linux?
>
> Our "disk" is 12x300GB in RAID5 (with 1 hot-spare) on a 3ware 9500-S12,
> so it's actually 2.7TiB ish. It's also /dev/sda - i.e., the one and
> only disk in the system.
>
> Problems are arising due to the 32-bit-ness of normal partition tables.
> I can use parted to make a 2.7TB partition (sda4), and
> /proc/partitions looks fine until a reboot, whereupon the top bits are
> lost and the big partition looks like a 700GB partition instead of a
> 2.7TB one; this is a bad thing ;-)
>
> I've had my hopes raised by GPT, but after more reading it appears this
> doesn't work on vanilla x86 PCs.
>
> Tips gratefully received.
>
> Neil
>
> PS: not on-list; I'll be reading the real-time archivers, but CCs of
> any replies would be appreciated.
Are you sure your card supports creating a single volume in excess of 2TB?
Some cards have such a limit, although you can create many 2TB volumes on the
same card.
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services group
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBwaueBn4EFUVUIO0RAhtLAKCK6ZcujlH1LGQ4SMssXlhoiifRqACgykSR
uXt8wfwTM2N6nxPBOFNaGtc=
=F7JI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-16 15:31 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 [this message]
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
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=200412161537.02804.m.watts@eris.qinetiq.com \
--to=m.watts@eris.qinetiq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nconway_kernel@yahoo.co.uk \
/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).