linux-ext4 - Ext4 bigalloc and sparc ext3 16k blocksize

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CALbEkhsi=Nqz=rfOApPsFi_Bk+cR5NE-VXcvVEZB3nC2MxebVA@mail.gmail.com>
Date:	Fri, 20 Jan 2012 12:20:28 +0100
From:	Bluflonalgul <bluflonalgul@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Ext4 bigalloc and sparc ext3 16k blocksize

Some (misleading?) article on kernelnewbies.org said the new Ext4
Bigalloc feature was about supporting block size up to 1MB.
I tried to use this feature to read an ext3 fs with 16k blocksize made
on a Linux Debian Sparc (NAS).
But I couldn't read such filesystem with the Linux 3.2 kernel on x86
PC... It fails to read fs structure (as it used to fail with previous
kernels).

Could someone point me to some documentation, or give me some clues:
I'd like to understand what's wrong and if I can hope to read such fs
with Linux on x86 (natively, without fusefs tricks or additional
tools).
Thanks.
B.
--
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