Thread (4 messages) 4 messages, 3 authors, 2011-07-20

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

From: Andreas Dilger <hidden>
Date: 2011-07-20 15:59:43

On 2011-07-19, at 11:38 PM, hao.bigrat@gmail.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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help