From: Erik Mouw <erik@harddisk-recovery.com>
To: Tomas Hruby <thruby@few.vu.nl>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: ext2/3 subdirectory limit [WAS: Choosing and tuning Linux file systems]
Date: Mon, 26 Jun 2006 14:59:00 +0200 [thread overview]
Message-ID: <20060626125859.GC3114@harddisk-recovery.com> (raw)
In-Reply-To: <20060626123635.GA15200@fspc268>
On Mon, Jun 26, 2006 at 02:36:35PM +0200, Tomas Hruby wrote:
> > > More than ~32,000 files in one directory: XFS or reiser
> >
> > Ext3 can easily have more than 32000 *files* in a directory. However,
> > it can only have 32000 *subdirectories* in a directory. This limit is
> > from struct ext3_inode->i_links_count, which is an __le16: each
> > subdirectory has an entry ".." that links back to its parent increasing
> > the parents i_links_count.
>
> I was always wondering why it increases link_count of the parent directory when
> creating a subdirectory. It is clear that .. points to the parent, but the
> subdirectory cannot exist without its parent and you cannot delete the parent if
> it is not empty. Correct me if I am wrong.
It is an elegant way: an inode can only be deleted when the link count
is zero. The fastest way to figure that out for directories would be to
let subdirs increase the parent link count: you just have look up the
link count in the parent instead of going through all directory entries
searching for possible subdirectories.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2006-06-26 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 22:00 Choosing and tuning Linux file systems Valerie Henson
2006-06-25 22:13 ` Matthew Wilcox
2006-06-25 22:26 ` Arjan van de Ven
2006-06-26 7:22 ` Neil Brown
2006-06-26 9:04 ` Nate Diller
2006-06-27 18:46 ` Valerie Henson
2006-06-26 11:10 ` Erik Mouw
2006-06-26 12:36 ` ext2/3 subdirectory limit [WAS: Choosing and tuning Linux file systems] Tomas Hruby
2006-06-26 12:35 ` Arjan van de Ven
2006-06-26 12:54 ` Theodore Tso
2006-06-26 16:25 ` Andreas Dilger
2006-06-26 17:35 ` Chris Wedgwood
2006-06-26 21:03 ` Tomas Hruby
2006-06-26 21:03 ` Chris Wedgwood
2006-06-26 21:13 ` H. Peter Anvin
2006-06-26 12:59 ` Erik Mouw [this message]
2006-06-26 21:09 ` Tomas Hruby
[not found] ` <20060626091357.GQ5817@schatzie.adilger.int>
2006-06-26 22:01 ` Choosing and tuning Linux file systems Valerie Henson
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=20060626125859.GC3114@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=thruby@few.vu.nl \
/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).