linux-ext4 - Re: Creating a >32bit blocks filesystem.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070509102940.36493474@gara>
Date:	Wed, 9 May 2007 10:29:40 -0500
From:	"Jose R. Santos" <jrs@...ibm.com>
To:	Valerie Clement <valerie.clement@...l.net>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Creating a >32bit blocks filesystem.

On Wed, 09 May 2007 16:57:01 +0200
Valerie Clement <valerie.clement@...l.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
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html