All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: suntrop@web.de
Cc: Andreas Dilger <adilger@dilger.ca>,
	Eric Sandeen <sandeen@redhat.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: File limit inside a single directory
Date: Fri, 13 Feb 2015 13:52:53 -0500	[thread overview]
Message-ID: <20150213185253.GB26115@thunk.org> (raw)
In-Reply-To: <trinity-232bc979-0b76-4776-a65c-b6697428d0a4-1423846162245@3capp-webde-bs16>

On Fri, Feb 13, 2015 at 05:49:22PM +0100, 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

In general the limitation you will hit first is one of performance,
rather than a hard limit.  Using nested directories, i.e.,
/home/t/y/t/tytso will generally be a performance win if you can do
it.

Cheers,

					- Ted

      parent reply	other threads:[~2015-02-13 18:52 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
2015-02-14 10:17         ` suntrop
2015-02-14 18:25           ` Andreas Dilger
2015-02-13 18:52       ` Theodore Ts'o [this message]

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=20150213185253.GB26115@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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.