From: Eric Sandeen <sandeen@redhat.com>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Valerie Clement <valerie.clement@bull.net>, linux-ext4@vger.kernel.org
Subject: Re: Creating a >32bit blocks filesystem.
Date: Wed, 09 May 2007 12:02:36 -0500 [thread overview]
Message-ID: <4641FEAC.9090203@redhat.com> (raw)
In-Reply-To: <20070509113428.760f453a@gara>
Jose R. Santos wrote:
> On Wed, 09 May 2007 10:21:44 -0500
> Eric Sandeen <sandeen@redhat.com> wrote:
>> Jose, you mentioned that some blocks are still "unsigned long" on
>> 32-bits... they shouldn't be, the LBD work should have fixed all those
>> long ago. But there is still the 16TB page cache limit in force.
>
> Found this in mke2fs.c
> unsigned long blocks = EXT2_BLOCKS_COUNT(fs->super);
> unsigned long start;
Ah, ok, I thought you were talking about kernelspace...
yeah, that looks like a problem. And it's from a patch called
"use_64bit_block_numbers" *grin*
there are a few related typedefs in e2fsprogs, such as blk_t, which is __u64
should we be using those for block number containers?
-Eric
next prev parent reply other threads:[~2007-05-09 17:05 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 [this message]
2007-05-09 15:29 ` Jose R. Santos
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=4641FEAC.9090203@redhat.com \
--to=sandeen@redhat.com \
--cc=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).