From: Eric Sandeen <sandeen@redhat.com>
To: suntrop@web.de, Andreas Dilger <adilger@dilger.ca>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: File limit inside a single directory
Date: Fri, 13 Feb 2015 11:28:34 -0600 [thread overview]
Message-ID: <54DE3442.90707@redhat.com> (raw)
In-Reply-To: <trinity-232bc979-0b76-4776-a65c-b6697428d0a4-1423846162245@3capp-webde-bs16>
On 2/13/15 10:49 AM, suntrop@web.de wrote:
> Thanks guys. I was afraid of having a couple 100K (at most). The
> server support team told me not to have more than 10 to 20K. There
> seems to be a misconception (for me and people from the CMS) about
> the 32K subdirectory limit, but this ins't for files/folders within a
> single directory but rather nested directories like /1/2/3.../32000
You've confused things a bit here, FWIW.
The 32k (well, 32000 because, sure) limit on ext3 is max link count;
each subdirectory increases the link count on its parent, but only
its parent. It's not about deep nesting, or about files in a dir.
It's only about subdirs in a parent dir.
# mkdir dir
# stat dir | grep Links
Device: fd06h/64774d Inode: 2490391 Links: 2 // . and .. entries
# mkdir dir/subdir1 dir/subdir2 dir/subdir3
# stat dir | grep Links
Device: fd06h/64774d Inode: 2490391 Links: 5
# mkdir dir/subdir1/subsubdir1 dir/subdir1/subsubdir2 dir/subdir1/subsubdir3
# stat dir | grep Links
Device: fd06h/64774d Inode: 2490391 Links: 5
ext4 bumped that max to 64000, and just stops counting if that number
gets exceeded...
-Eric
next prev parent reply other threads:[~2015-02-13 17:28 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
[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 [this message]
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=54DE3442.90707@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@dilger.ca \
--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 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.