From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Christoph Hellwig <hch@infradead.org>,
"Peter J. Braam" <braam@clusterfs.com>,
linux-kernel@vger.kernel.org
Subject: Re: BIG files & file systems
Date: Wed, 31 Jul 2002 23:04:12 +0300 [thread overview]
Message-ID: <20020731230412.B1237@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020731202638.A22765@infradead.org>; from hch@infradead.org on Wed, Jul 31, 2002 at 08:26:38PM +0100
On Wed, Jul 31, 2002 at 08:26:38PM +0100, Christoph Hellwig wrote:
> On Wed, Jul 31, 2002 at 01:16:20PM -0600, Peter J. Braam wrote:
> > Hi,
> >
> > I've just been told that some "limitations" of the following kind will
> > remain:
> >
> > page index = unsigned long
> > ino_t = unsigned long
> >
> > Lustre has definitely been asked to support much larger files than
> > 16TB. Also file systems with a trillion files have been requested by
> > one of our supporters (you don't want to know who, besides I've no
> > idea how many bits go in a trillion, but it's more than 32).
>
> What about using 64bit machines? ..
It depends on many things:
- Block layer (unsigned long)
- Page indexes (unsigned long)
- Filesystem format dependent limits
- EXT2/EXT3: u32_t FILESYSTEM block index, presuming the EXT2/EXT3
is supported only up to 4 kB block sizes, that gives
you a very hard limit.. of 16 terabytes (16 * "10^12")
- ReiserFS: u32_t block indexes presently, u64_t in future;
block size ranges ? Max size is limited by the
maximum supported file size, likely 2^63, which is
roughly 8 * "10^18", or circa 500 000 times larger
than EXT2/EXT3 format maximum.
- ClusterFS: (Braam et.al.): 64 bit block indexes ?
System file size limitation, same as with ReiserFS.
(Just to illustriate a few..)
/Matti Aarnio
next prev parent reply other threads:[~2002-07-31 20:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 19:16 BIG files & file systems Peter J. Braam
2002-07-31 19:26 ` Christoph Hellwig
2002-07-31 20:04 ` Matti Aarnio [this message]
2002-07-31 20:12 ` Christoph Hellwig
2002-08-02 17:26 ` Albert D. Cahalan
2002-08-02 22:14 ` Randy.Dunlap
2002-08-03 3:26 ` Albert D. Cahalan
2002-08-06 5:19 ` Andreas Dilger
2002-08-06 7:24 ` Albert D. Cahalan
2002-08-06 7:52 ` Andreas Dilger
2002-08-06 9:28 ` Matti Aarnio
2002-08-05 13:04 ` Stephen Lord
2002-08-05 13:42 ` Hans Reiser
2002-08-05 13:56 ` Randy.Dunlap
2002-08-05 14:21 ` Randy.Dunlap
2002-08-05 17:31 ` Albert D. Cahalan
2002-08-06 0:16 ` jw schultz
2002-08-06 9:48 ` Hans Reiser
2002-07-31 21:07 ` Jan Harkes
2002-07-31 21:13 ` Alexander Viro
2002-08-01 3:51 ` Jan Harkes
2002-08-01 12:01 ` Mark Mielke
2002-08-02 0:09 ` Stephen Lord
2002-08-02 12:17 ` Chris Mason
2002-08-02 12:33 ` Anton Altaparmakov
2002-08-02 13:56 ` Jan Harkes
2002-08-02 14:06 ` Steve Lord
2002-08-02 15:10 ` Hans Reiser
2002-08-02 15:39 ` Trond Myklebust
2002-08-02 17:01 ` Hans Reiser
2002-08-02 17:25 ` Nikita Danilov
2002-08-02 17:47 ` Trond Myklebust
2002-08-02 18:10 ` Nikita Danilov
2002-08-02 18:31 ` Hans Reiser
2002-08-02 18:48 ` Nikita Danilov
2002-08-02 18:59 ` Hans Reiser
2002-08-01 12:01 ` David Woodhouse
2002-08-01 20:33 ` Andrew Morton
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=20020731230412.B1237@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=braam@clusterfs.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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