From: Eric Sandeen <sandeen@redhat.com>
To: suntrop@web.de, linux-ext4@vger.kernel.org
Subject: Re: File limit inside a single directory
Date: Thu, 12 Feb 2015 13:35:45 -0600 [thread overview]
Message-ID: <54DD0091.1050104@redhat.com> (raw)
In-Reply-To: <trinity-2286fbea-64f2-4a0a-b0a7-2d7fc4f6f180-1423768604697@3capp-webde-bs55>
On 2/12/15 1:16 PM, suntrop@web.de wrote:
> Hello, i’m using a CMS which puts many files inside a single
> directory. I’m wondering what the maximum number of files is which
> can reside inside said directory. Is there a number which should not
> be exceeded on account of performance reasons e.g. Is there a
> difference between ext3 and ext4?
>
> Thanks!
for htree directories, you will be limited by the max size of the tree, which currently is of limited depth. That limit then depends on block size and filename lengths.
for 4k blocks, and 40 char names, you max out at around 20 million directory entries, if my old spreadsheet is still correct.
That limit is the same for ext3 and ext4.
performance-wise, to be honest, I'm not sure. how many inodes are you talking about?
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-12 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 19:16 File limit inside a single directory suntrop
2015-02-12 19:35 ` Eric Sandeen [this message]
[not found] ` <trinity-18fd0cfe-2cce-4517-bfdc-031a7a4a4e80-1423772290927@3capp-webde-bs55>
[not found] ` <54DD0B7B.7020002@redhat.com>
2015-02-12 20:35 ` suntrop
2015-02-13 0:55 ` Andreas Dilger
2015-02-13 16:49 ` suntrop
2015-02-13 17:28 ` Eric Sandeen
2015-02-14 10:17 ` suntrop
2015-02-14 18:25 ` Andreas Dilger
2015-02-13 18:52 ` Theodore Ts'o
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=54DD0091.1050104@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=suntrop@web.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).