From: Andreas Dilger <adilger@clusterfs.com>
To: Michal Jaegermann <michal@harddata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: max partition size
Date: Fri, 22 Mar 2002 01:42:09 -0700 [thread overview]
Message-ID: <20020322084209.GD3451@turbolinux.com> (raw)
In-Reply-To: <20020322005037.A9256@mail.harddata.com>
On Mar 22, 2002 00:50 -0700, Michal Jaegermann wrote:
> Who knows for sure what is the current upper limit on ext2/ext3
> file system size (4KiB blocks as this is what tools will accept)? It
> definitely is not 1 TB as we were making working partition nearly twice
> that. But practice seems to indicate that 2 TB, or whereabout, can be
> too much. Is this a property of a file system or we bumping into
> block device boundaries or this are just tools?
2TB is the limit for all block devices in 2.2 and 2.4 kernels. This is
from 2^32 * 512 byte sectors. Using LVM or MD devices will not overcome
this limitation.
There was a patch floating around which extended the block counts to
64-bit ints (Jens Axboe and/or Ben LaHaise posted it), and I think at
least part of it is in 2.5. Even if you have 64-bit block counts,
there are other issues which pop up fairly soon - 32-bit page indexes
and other 32-bit overflows in calculations in the ext2 code. There
is definitely a hard limit at 16TB for 4kB block ext2 filesystems,
but I suspect you will have problems at 8TB even after the 2TB block
device limit is lifted.
> BTW - mke2fs goes most of the way but gets stuck eventually when
> writing inode tables if that it is too close to 2 TB. Yes, there
> are people who really want that much of a file system or maybe even
> more. :-) This was not done for a sake of a record.
You could always try it on a real 64-bit machine to see if that helps.
You can concievably use 8kB blocks on an Alpha, giving you an upper
limit of 32TB for the filesystem until the ext2 extent code is
implemented (which will give us 64-bit block numbers among other things).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2002-03-22 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 7:50 max partition size Michal Jaegermann
2002-03-22 8:42 ` Andreas Dilger [this message]
2002-03-22 14:58 ` Alan Cox
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=20020322084209.GD3451@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@harddata.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