linux-kernel - Re: ext3_dx_add_entry: Directory index full!

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, 19 May 2008 01:01:57 +0200
From:	Stefano Fedrigo <aleph@...eler.com>
To:	Theodore Tso <tytso@....edu>
Cc:	Bernie Innocenti <bernie@...ewiz.org>,
	lkml <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>, ext3-users@...hat.com,
	ext2-devel@...ts.sourceforge.net
Subject: Re: ext3_dx_add_entry: Directory index full!

On May 18, 2008, at 6:24 PM, Theodore Tso wrote:

> No, not a bug, but a limit.  Ext3's hash directores are limited to a
> depth of 3 blocks, which normally isn't a problem if you are using a
> 4k blocksize, since each internal node is small; only 8 bytes.  So you
> have a fanout of 508 for each internal node, and two internal nodes
> gets you to over 250,000 4k directory blocks.  But with a 1k
> blocksize, the internal node fanout is only 124, so that only gets you
> a bit more than 15,000 1k directory blocks.

So, if I understand correctly, with a 1024 bytes blocksize, dir_index,  
and inode size of 128 byte, the maximum number of files in a directory  
is 123008.  With 4k blocks this limit rises to 8,258,048 files?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/