linux-ext4 - Re: [PATCH bigalloc] e2fsprogs: change root-inode to extent-mapped

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: <B27D0C6A-E0F5-4196-872B-392AA72FB348@gmail.com>
Date:	Wed, 20 Jul 2011 09:52:49 -0600
From:	Andreas Dilger <aedilger@...il.com>
To:	"hao.bigrat@...il.com" <hao.bigrat@...il.com>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	Robin Dong <sanbai@...bao.com>, Ted Ts'o <tytso@....edu>
Subject: Re: [PATCH bigalloc] e2fsprogs: change root-inode to extent-mapped

On 2011-07-19, at 11:38 PM, hao.bigrat@...il.com wrote:
> 
> After creating more than 1000 files in root directory on ext4 of bigalloc,
> the kernel reports many error messages like:
> 
> [181126.730911] EXT4-fs error (device sda4): ext4_ind_map_blocks:1015: inode #2: comm falloc: Can't allocate blocks for non-extent mapped inodes with bigalloc
> [181126.735945] EXT4-fs error (device sda4): ext4_ind_map_blocks:1015: inode #2: comm falloc: Can't allocate blocks for non-extent mapped inodes with bigalloc
> 
> because the root inode of a new ext4 filesystem is type of block-mapped
> even use mke2fs with "-O extent,bigalloc".

That reminds me of a question I had with bigalloc - are htree directories supported with bigalloc?  For a 1MB bigalloc chunksize it would mean a fanout of 256k, or a maximum directory size of 256GB with only a single level.

Any thoughts about increasing the directory size beyond 2GB?

Cheers, Andeas--
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