linux-ext4 - Re: 16 TB filesystem limit on 32bit machine

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]

Date:	Mon, 20 Feb 2012 16:17:31 -0500
From:	Phillip Susi <psusi@...ntu.com>
To:	Eric Sandeen <sandeen@...hat.com>
CC:	Rabeeh Khoury <rabeeh3000@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: 16 TB filesystem limit on 32bit machine

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/20/2012 11:50 AM, Eric Sandeen wrote:
> fs metadata is mapped into an address space, IIRC, so can't be
> addressed past 2^32 pages.  Also, mkfs can't do buffered IO to the
> device past 16T (it is writing to a device _file_) and ditto for
> e2fsck.

But the file is only used for open(), after that the IO is handled by
the correct device driver, which handles 64 bit offsets ( when you
have CONFIG_LBDAF on ).  So if you can change the page cache index
size ( and it doesn't blow up ) this should work fine.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPQrhrAAoJEJrBOlT6nu75yX8IAKNmJv0tH2CMWefUFV/4un0g
NKU5L2uwuMmyAzVRUOv165d1KAJkNc0z3OLUyh3425yku6wQ4dDqqnWSHCIZHJs7
/d1ltEP1g/vhpM5keAwwWHfC7N2KL+FRyqze8YAe6Qx5GGEWlUOqK2ALSxtuL2Il
TQ+lfLI9kAA5Ggtwf6mjjD/fKFTdJILQuZikxpJRfKasLg/4Y25LWdaPG8BOm78l
qPxkazpmIG8HVFczHwVWpuu+xY8nAmgDdZCTJBFoK9xmBUO0kjzl8JlAl4ScaXdi
v1793CSzev/2aIhEwXSK0HdI7e6KI4iT292/k4ryjfwJ+QX5L6eyfd4HlSVMM88=
=IOG0
-----END PGP SIGNATURE-----
--
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