public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Maximum files per Directory
Date: Fri, 04 May 2001 16:08:22 -0400	[thread overview]
Message-ID: <392230000.989006902@tiny> (raw)
In-Reply-To: <200105041915.f44JFNeM024068@webber.adilger.int>



On Friday, May 04, 2001 01:15:22 PM -0600 Andreas Dilger
<adilger@turbolinux.com> wrote:

> Chris writes:
>> On Tuesday, May 01, 2001 04:57:02 PM -0600 Andreas Dilger
>> <adilger@turbolinux.com> wrote:
>> > I see that reiserfs plays some tricks with the directory i_nlink count.
>> > If you exceed 64536 links in a directory, it reverts to "1" and no
>> > longer tracks the link count.
>> 
>> Correct.  The link count isn't used at all when deciding if the directory
>> is empty (we use the size instead), so we can just lie to VFS if someone
>> tries to make tons of subdirs.
> 
> For that matter, ext2 doesn't use the link count on directories to
> determine if they are empty either, so it shouldn't be too hard to do the
> same with the ext2 indexed-directory code.  Is there a reason that
> reiserfs chose to have "large number of directories" represented by "1"
> and not "LINK_MAX+1"?
> 

find and a few others consider a link count of 1 to mean there is no link
count tracking being done.

-chris


  reply	other threads:[~2001-05-04 20:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01 20:48 Maximum files per Directory Andreas Rogge
2001-05-01 20:58 ` H. Peter Anvin
2001-05-01 22:57   ` Andreas Dilger
2001-05-04 13:49     ` Chris Mason
2001-05-04 19:15       ` Andreas Dilger
2001-05-04 20:08         ` Chris Mason [this message]
2001-05-05 13:49           ` Jamie Lokier
2001-05-05 16:16             ` Chris Mason
2001-05-01 21:02 ` Alan Cox
2001-05-01 22:03   ` H. Peter Anvin
2001-05-02 10:22     ` Ingo Oeser
2001-05-02 16:13       ` H. Peter Anvin
2001-05-02 13:33   ` Ketil Froyn
2001-05-02  9:21 ` Henning P. Schmiedehausen

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=392230000.989006902@tiny \
    --to=mason@suse.com \
    --cc=adilger@turbolinux.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox