From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Mike Eldridge <diz@cafes.net>
Cc: Marcelo Borges Ribeiro <marcelo@datacom-telematica.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: Filesize limit on SMBFS
Date: Sat, 24 Nov 2001 03:16:25 +0200 [thread overview]
Message-ID: <20011124031625.T2682@mea-ext.zmailer.org> (raw)
In-Reply-To: <Pine.LNX.4.42.0111231034330.15987-100000@boston.corp.fedex.com> <002801c1740f$7372f650$1300a8c0@marcelo> <20011123171157.Q21290@mail.cafes.net>
In-Reply-To: <20011123171157.Q21290@mail.cafes.net>; from diz@cafes.net on Fri, Nov 23, 2001 at 05:11:57PM -0600
On Fri, Nov 23, 2001 at 05:11:57PM -0600, Mike Eldridge wrote:
> ext2 has a 2GB filesize limitation.
Mike has already realized this, but still...
I have used ext2 at Linux 1.2 with file sizes exceeding 2GB.
The requirement was 64 bit machine in those days, I had Alpha.
(Yes, that was VERY LONG AGO!)
It is very late (2.3/2.4) development that 32-bit machines can
do 2TB files. Sparse files can indeed be larger up to 4G times
filesystem block size, but ext2 is limited on one physical
partition, and those are still limited on 1 or 2 terabyte range.
(2G * 512 or 4G * 512.) (long story why that limit is still
in there, mainly because nobody has had need to rework it.)
Limitations on EXT2 (indeed of all "indirect block indexing"
schemes of SysV FS style) are a bit complicated to calculate.
B = block size in bytes (512 to 4096 bytes)
addressable_blocks = (B/4)**3 + (B/4)**2 + ...
max_offset = B * addressable_blocks
So, say: max_offset = B**4 / 64 + epsilon
That gives you magnitude. Say with 4k blocks (long story why that
is presently maximum block-size) you can have up to 4 TB file size.
(plus a bit over, see the math.)
The 2.5 series may change the underlying block-device layer so that
it can handle larger block devices than 2TB - the 64 bit machines can
handle them, of course, but 32-bit i386 is a bit limited...
> -mike
> radiusd+mysql: http://www.cafes.net/~diz/kiss-radiusd
/Matti Aarnio
next prev parent reply other threads:[~2001-11-24 1:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 18:53 Tyler BIRD
2001-11-22 19:23 ` Marcelo Borges Ribeiro
2001-11-22 19:57 ` Andreas Dilger
2001-11-23 2:35 ` Jeff Chua
2001-11-23 11:10 ` Marcelo Borges Ribeiro
2001-11-23 12:00 ` Jeff Chua
2001-11-23 23:11 ` Mike Eldridge
2001-11-23 23:19 ` war
2001-11-23 23:19 ` Andreas Dilger
2001-11-23 23:45 ` Mike Eldridge
2001-11-24 1:16 ` Matti Aarnio [this message]
2001-11-24 20:43 ` Eric W. Biederman
2001-11-26 18:27 ` Alan Cox
2001-11-23 2:49 ` Anton Altaparmakov
2001-11-23 3:27 ` Jeff Chua
2001-11-23 7:09 ` OGAWA Hirofumi
2001-11-24 9:08 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 9:10 Petr Tite(ra
2001-11-22 12:10 ` Urban Widmark
2001-11-22 13:01 ` Petr Titera
2001-11-22 20:58 ` Urban Widmark
2001-11-22 13:21 ` Anton Altaparmakov
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=20011124031625.T2682@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=diz@cafes.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@datacom-telematica.com.br \
/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®