From: "Jose R. Santos" <jrs@us.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Creating a >32bit blocks filesystem.
Date: Wed, 9 May 2007 10:29:40 -0500 [thread overview]
Message-ID: <20070509102940.36493474@gara> (raw)
In-Reply-To: <4641E13D.906@bull.net>
On Wed, 09 May 2007 16:57:01 +0200
Valerie Clement <valerie.clement@bull.net> wrote:
> Jose R. Santos wrote:
> > I think this has more to do with the fact that I'm on a 32bit
> > architecture and there are still a couple places where blocks are
> > represented using "unsigned long". I'm trying to get access to a 64bit
> > arch to confirm this.
> >
> > -JRS
> >
> Oh, I didn't catch that you use a 32-bit system.
> On 32-bit architectures, the page cache index size imposes a 16TB limit
> on the filesystem size (with 4KB blocksize). So you need a 64-bit system
> for your test.
> Valérie
Thanks for the info. Would the page cache limitation also restrict debugfs and dumpe2fs from reading information on a large filesystem? Would a check need to be in place to limit the use of e2fsprog on 32bit architectures using large block devices.
-JRS
next prev parent reply other threads:[~2007-05-09 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 19:08 Creating a >32bit blocks filesystem Jose R. Santos
2007-05-04 14:58 ` Valerie Clement
2007-05-07 16:19 ` Jose R. Santos
2007-05-07 18:36 ` Jose R. Santos
2007-05-09 12:16 ` Valerie Clement
2007-05-09 13:55 ` Jose R. Santos
2007-05-09 14:57 ` Valerie Clement
2007-05-09 15:21 ` Eric Sandeen
2007-05-09 16:34 ` Jose R. Santos
2007-05-09 17:02 ` Eric Sandeen
2007-05-09 15:29 ` Jose R. Santos [this message]
2007-05-09 16:15 ` Andreas Dilger
2007-05-09 17:18 ` Eric Sandeen
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=20070509102940.36493474@gara \
--to=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=valerie.clement@bull.net \
/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;
as well as URLs for NNTP newsgroup(s).