All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: Adam Voigt <adam@cryptocomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File Limit in Kernel?
Date: Tue, 12 Nov 2002 11:01:49 -0500	[thread overview]
Message-ID: <20021112110149.A9492@borg.org> (raw)
In-Reply-To: <1037115535.1439.5.camel@beowulf.cryptocomm.com>; from adam@cryptocomm.com on Tue, Nov 12, 2002 at 10:38:55AM -0500

On Tue, Nov 12, 2002 at 10:38:55AM -0500, Adam Voigt wrote:
> I have a directory with 39,000 files in it, and I'm trying to use the cp
> command to copy them into another directory, 
> [...]
> "argument list too long"

No, it is not a kernel limit, it is a limit to your shell (bash, for
example).  Look at xargs to get around it.

A related limit is that the popular ext2 and 3 file systems get
inefficient when directories have so many files.  The work-around for
that is to have your files either hashed or organized across a
collection of directories.


-kb

  parent reply	other threads:[~2002-11-12 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 15:38 File Limit in Kernel? Adam Voigt
2002-11-12 15:57 ` Andreas Gruenbacher
2002-11-13  9:51   ` Jan Hudec
2002-11-13 10:49     ` Andreas Schwab
2002-11-12 16:01 ` Kent Borg [this message]
2002-11-12 16:26   ` Mark Mielke
2002-11-12 16:06 ` Chris Friesen
2002-11-12 16:08 ` Richard B. Johnson
2002-11-12 16:12 ` Matt Reppert
2002-11-12 16:16 ` Bernd Eckenfels
2002-11-12 23:23 ` Bill Davidsen
     [not found] <1037115535.1439.5.camel@beowulf.cryptocomm.com.suse.lists.linux.kernel>
2002-11-12 15:53 ` Andi Kleen
2002-11-12 21:54   ` Pavel Machek
2002-11-19 15:14     ` Shalon Wood
2002-11-19 19:44       ` Pavel Machek
2002-11-12 21:55   ` Jamie Lokier

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=20021112110149.A9492@borg.org \
    --to=kentborg@borg.org \
    --cc=adam@cryptocomm.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 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.