From: "Joseph Shamash" <info@avistor.com>
To: "Mike Fedyk" <mfedyk@matchmail.com>,
"Peter Chubb" <peter@chubb.wattle.id.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: 2 TB partition support
Date: Mon, 10 Nov 2003 20:03:53 -0800 [thread overview]
Message-ID: <HBEHKOEIIJKNLNAMLGAOOEDFDKAA.info@avistor.com> (raw)
In-Reply-To: <16304.23206.924374.529136@wombat.chubb.wattle.id.au>
>What exactly are you trying to do?
Doing testing in our lab trying to use 2.4.x and 2.6.
Trying to see how high a storage capacity can be supported
above 2TB, both in partitions and file sizes.
The limitation we have found in 2.4 is lack of 2TB support,
(using hardware raid with 2TB+ partitions).
The limitation we have found in 2.6 is lack FC HBA drivers which
are needed to support large storage capacities.
Any thoughts?
-----Original Message-----
From: Peter Chubb [mailto:peterc@chubb.wattle.id.au]On Behalf Of Peter
Chubb
Sent: Monday, November 10, 2003 7:43 PM
To: Mike Fedyk
Cc: Joseph Shamash; Peter Chubb; linux-kernel@vger.kernel.org
Subject: Re: 2 TB partition support
>>>>> "Mike" == Mike Fedyk <mfedyk@matchmail.com> writes:
> On Mon, Nov 10, 2003 at 06:12:06PM -0800, Joseph Shamash wrote:
>>
>> What is the maximum partition size for a patched 2.4.x kernel, and
>> where are those patches?
Mike> I believe it is now 16TB per block device in 2.6, and patched
Mike> 2.4.
That's right for 32-bit systems with 4k pages. For 64 bit systems the
limit is over 8 Exabytes.
You should note that software raid has smaller limits, as does the
LVM. Also the 2.4 patches have seen *much* less testing than the 2.6
mainline (except possibly on the SGI Altix).
What exactly are you trying to do?
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
The technical we do immediately, the political takes *forever*
next prev parent reply other threads:[~2003-11-11 4:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 21:17 Joseph Shamash
2003-11-10 23:56 ` Peter Chubb
2003-11-11 2:10 ` Joseph Shamash
2003-11-11 2:20 ` Mike Fedyk
2003-11-11 2:12 ` Joseph Shamash
2003-11-11 2:21 ` Mike Fedyk
2003-11-11 3:42 ` Peter Chubb
2003-11-11 4:03 ` Joseph Shamash [this message]
2003-11-11 5:30 ` Patrick Mansfield
2003-11-11 21:21 ` Joseph Shamash
2003-11-11 23:58 ` Patrick Mansfield
2003-11-12 22:54 ` Randy.Dunlap
2003-11-11 2:39 ` Peter Chubb
2003-11-11 2:52 ` Joseph Shamash
2003-11-11 2:53 ` Neil Brown
2003-11-12 0:28 ` Bernd Schubert
2003-11-12 3:44 ` Mike Fedyk
2003-11-12 19:35 ` Peter Chubb
2003-11-14 17:14 ` Bernd Schubert
2003-11-14 17:43 ` Mike Fedyk
2003-11-12 0:01 Xose Vazquez Perez
[not found] <QugF.3Mq.7@gated-at.bofh.it>
[not found] ` <Qwit.771.11@gated-at.bofh.it>
[not found] ` <QR40.39P.53@gated-at.bofh.it>
2003-11-12 0:45 ` Andi Kleen
2003-11-12 19:37 ` Peter Chubb
2003-11-12 22:26 ` Andi Kleen
2003-11-12 11:09 ` Hans Reiser
2003-11-12 23:45 ` Peter Chubb
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=HBEHKOEIIJKNLNAMLGAOOEDFDKAA.info@avistor.com \
--to=info@avistor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=peter@chubb.wattle.id.au \
/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®