When using hash index, too many long-subdirectory-names and 1024 blocksize, the subdirectory limit may be less than 32000. The problem is that indexed diretories have a limit that only allows the trees to be two levels deep. The fanout is normally big enough that this is effectively not a problem, but if you use too many long-names, and a 1024 blocksize, you will run into htree limit much more quickly. The users may be puzzled when they can't create more than 32000 subdirecties with using hash index, too many long-names and 1024 blocksize. It should be remind of in the ext4 document. Signed-off-by: Zhang Xiliang <zhangxiliang@xxxxxxxxxxxxxx> --- Documentation/filesystems/ext4.txt | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-) diff --git a/Documentation/filesystems/ext4.txt b/Documentation/filesystems/ext4.txt index cec829b..0e1ec9c 100644 --- a/Documentation/filesystems/ext4.txt +++ b/Documentation/filesystems/ext4.txt @@ -85,7 +85,7 @@ Note: More extensive information for getting started with ext4 can be * extent format more robust in face of on-disk corruption due to magics, * internal redundancy in tree * improved file allocation (multi-block alloc) -* fix 32000 subdirectory limit +* fix 32000 subdirectory limit (*1) * nsec timestamps for mtime, atime, ctime, create time * inode version field on disk (NFSv4, Lustre) * reduced e2fsck time via uninit_bg feature @@ -100,6 +100,12 @@ Note: More extensive information for getting started with ext4 can be * efficent new ordered mode in JBD2 and ext4(avoid using buffer head to force the ordering) +(*1) Note +Basically, the limit depends on blocksize and length of subdirectory names in +the directory. If blocksize is too small (like 1024) and you use too many +long-names, you may reach a smaller limit. When dir index is off, the limit is +65000. + 2.2 Candidate features for future inclusion * Online defrag (patches available but not well tested) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
