linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Tomas Hruby <thruby@few.vu.nl>
Cc: Theodore Tso <tytso@mit.edu>,
	Erik Mouw <erik@harddisk-recovery.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: ext2/3 subdirectory limit [WAS: Choosing and tuning Linux file systems]
Date: Mon, 26 Jun 2006 14:03:41 -0700	[thread overview]
Message-ID: <20060626210341.GB28032@tuatara.stupidest.org> (raw)
In-Reply-To: <20060626210357.GA4308@fspc268>

On Mon, Jun 26, 2006 at 11:03:57PM +0200, Tomas Hruby wrote:

> So if I have a directory where the nlink does not correspond with
> then number of subdirectories, the applications you mentined don't
> work correctly?

yes

> As Ted said, not all fiel systems follow this. This means that such
> applications cannot e.g., remove a directory (rm -r) from such a FS?

i don't know about rm, but some versions of find need -noleaf (see the
man page for details)

> I am asking because we have an issue that an older version of mc
> cannot remove directory recursively, however we have not observed
> this on any new system. Might the nlink count be the problem?

i'm not seen the nlink problem occur because pretty much all
filesystems have nlink set correctly *or* they set it to one like
autofs does which happens to work because 1-2-n underflows (there are
also those who claim that nlink==1 implies you don't know how many
links there are)


  reply	other threads:[~2006-06-26 21:03 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 [this message]
2006-06-26 21:13             ` H. Peter Anvin
2006-06-26 12:59     ` Erik Mouw
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=20060626210341.GB28032@tuatara.stupidest.org \
    --to=cw@f00f.org \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=thruby@few.vu.nl \
    --cc=tytso@mit.edu \
    /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).