From: Olaf Hering <olaf@aepfle.de>
To: Andreas Dilger <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext3_dx_add_entry complains about Directory index full
Date: Wed, 4 Feb 2015 14:52:16 +0100 [thread overview]
Message-ID: <20150204135215.GA15159@aepfle.de> (raw)
In-Reply-To: <FCD1EFFD-330A-4953-8CF4-AC88D297F433@dilger.ca>
On Wed, Feb 04, Andreas Dilger wrote:
> How many files/subdirs in this directory? The old ext3 limit was 32000
> subdirs, which the dir_index fixed, but the new limit is 65000 subdirs
> without "dir_index" enabled.
See below:
> > # for t in d f l ; do echo "type $t: `find /media/BACKUP_OLH_500G/ -xdev -type $t | wc -l`" ; done
> > type d: 1051396
> > type f: 20824894
> > type l: 6876
> The 65000 subdir limit can be exceeded by turning on the "dir_nlink"
> feature of the filesystem with "tune2fs -O dir_nlink", to allow an
> "unlimited" number of subdirs (subject to other directory limits, about
> 10-12M entries for 16-char filenames).
I enabled this using another box, which turned the thing into an ext4
filesystem. Now ext4_dx_add_entry complains.
> The other potential problem is if you create and delete a large number
> of files from this directory, then the hash tables can become full and
> the leaf blocks are imbalanced and some become full even when many others
> are not (htree only has an average leaf fullness of 3/4 of each block).
> This could probably happen if you have more than 5M files in a long-lived
> directory in your backup fs. This can be fixed (for some time at least)
> via "e2fsck -fD" on the unmounted filesystem to compact the directories.
Ok, will try that. Thanks.
Olaf
next prev parent reply other threads:[~2015-02-04 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 9:04 ext3_dx_add_entry complains about Directory index full Olaf Hering
2015-02-04 10:52 ` Andreas Dilger
2015-02-04 13:52 ` Olaf Hering [this message]
2015-02-04 16:30 ` Olaf Hering
2015-02-04 21:32 ` Andreas Dilger
2015-02-05 9:19 ` Olaf Hering
2015-02-06 6:52 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150204135215.GA15159@aepfle.de \
--to=olaf@aepfle.de \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.