From: Yuri Csapo <ycsapo@mines.edu>
To: Beginner <dermot@sciencephoto.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Files per directory
Date: Thu, 10 Jul 2008 11:52:03 -0600 [thread overview]
Message-ID: <48764C43.9030300@mines.edu> (raw)
In-Reply-To: <4874E7D2.25203.1EFD94B4@dermot.sciencephoto.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Beginner wrote:
>
> Is that going to cause performance issues? The current file system
> ext3. Would anyone suggest a limit I should set for the maximum or
> say if they think 10K files is acceptable?
>
I'm no expert but the answer is probably: "depends on the application."
As far as I know there's no limit to the number of files in a directory
currently in ext3. There IS a limit to the number of files (actually
inodes) in the whole filesystem, which is a completely different thing.
According to Wikipedia "If V is the volume size in bytes, then the
default number of inodes is given by V/2^13 (or the number of blocks,
whichever is less)." There's also a limit to the number of
sub-directories in a directory, currently 32000.
What I can tell you is I have seen applications that use hundreds of
thousands of files in one directory.
HTH
--
Yuri Csapo
Academic Computing & Networking
Colorado School of Mines
CT-256
Phone: (303) 273-3503
Fax: (303) 273-3475
Email: ycsapo@mines.edu
Please use the following link to open a service request:
http://helpdesk.mines.edu
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2840 bytes --]
next prev parent reply other threads:[~2008-07-10 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 15:31 Files per directory Beginner
2008-07-10 17:52 ` Yuri Csapo [this message]
2008-07-10 20:55 ` Glynn Clements
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=48764C43.9030300@mines.edu \
--to=ycsapo@mines.edu \
--cc=dermot@sciencephoto.com \
--cc=linux-admin@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.