mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: mfedyk@matchmail.com, info@avistor.com, linux-kernel@vger.kernel.org
Subject: Re: 2 TB partition support
Date: Wed, 12 Nov 2003 14:54:12 -0800	[thread overview]
Message-ID: <20031112145412.226c789f.rddunlap@osdl.org> (raw)
In-Reply-To: <16304.23206.924374.529136@wombat.chubb.wattle.id.au>

On Tue, 11 Nov 2003 14:42:30 +1100 Peter Chubb <peter@chubb.wattle.id.au> wrote:

| >>>>> "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?


I made the table below for LinuxWorld Expo/Conference in Aug. 2002,
for Linux 2.4.x on 32-bit architectures, so it is a bit out of date,
but it might be helpful or useful.

--
~Randy
MOTD:  Always include version info.





Linux 2.4 filesystem limits on 32-bit architectures,
with 4 KB block sizes:


                     ext2/3fs    reiserfs     JFS       XFS#
max filesize:          4 TB&      16 TB$     16 TB$%  16 TB$
max filesystem size:  16 TB&      16 TB&     16 TB$   16 TB$
		                              4 PB&    8 EB&
kernel bldev limit:    2 TB        2 TB       2 TB     2 TB 


Notes:
#: all kernel limits
$: kernel limit
%: 4 KB pages
@: block device limit: 2 TB (or 1 TB if signed)
&: fs limit



Another look at ext2/3fs limits:

  Assumes using 4 KB block sizes on a 32-bit architecture
  (64-bit architecture isn't very limiting).

Largest limiting factor
           |
	   v
Smallest limiting factor


1.  64-bit API limit:  8 EiB

2.  kernel page cache index limit (32 bits) == filesystem block number:
    2^32 * 4 KB = 16 TiB

3.  ext2fs triple-indirect block limit:  4 TiB

4.  kernel block device limit (device sector number):  2 TiB
    (or 1 TiB if signed)

###

  parent reply	other threads:[~2003-11-12 22:58 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
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 [this message]
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=20031112145412.226c789f.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=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®