From: Andi Kleen <ak@suse.de>
To: Adam Voigt <adam@cryptocomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File Limit in Kernel?
Date: 12 Nov 2002 16:53:26 +0100 [thread overview]
Message-ID: <p738yzywzrd.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Adam Voigt's message of "12 Nov 2002 16:45:43 +0100"
Adam Voigt <adam@cryptocomm.com> writes:
> --=-gjU1b+qYiuNy2hSLpQYr
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> 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, and neither the cp or the
> mv command will work, they both same "argument list too long" when I
> use:
>
> cp -f * /usr/local/www/images
Kind of. The * is expanded by the shell. The kernel limits the max
length of program arguments, which is biting you here. In theory you
could increase the MAX_ARG_PAGES #define in linux/binfmts.h and
recompile. No guarantee that it won't have any bad side effects
though. The default is rather low, it should be probably increased
(I also regularly run into this)
The actual limit of files per directory is usually around 65000 in
most fs.
For your immediate problem you can use
find -type f | xargs cp -iX -f X /usr/local/www/images
-Andi
next parent reply other threads:[~2002-11-12 15:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1037115535.1439.5.camel@beowulf.cryptocomm.com.suse.lists.linux.kernel>
2002-11-12 15:53 ` Andi Kleen [this message]
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
2002-11-12 15:38 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
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
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=p738yzywzrd.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®