I have a directory with thousands of files. How can I move 100 of the files (any files will do) to another location.

  • Because Unix and Linux dont have one big website about its tools, so I simply go to website like about.com and some other website for the list of options available that I can possibly use.. but found nothing like tail – gaijin May 11 '11 at 1:53

13 Answers 13

up vote 34 down vote accepted
for file in $(ls -p | grep -v / | tail -100)
mv $file /other/location

That assumes file names don't contain blanks, newline (assuming the default value of $IFS), wildcard characters (?, *, [) or start with -.

  • 12
    Note that this approach only works if there are no special characters (whitespace, nonprintable characters, ``) in the file names. As a general rule, do not parse the output of ls. And always double-quote parameter and command substitutions. – Gilles May 11 '11 at 7:20
  • 1
    Which part accounts for 100 files? – Tshepang May 11 '11 at 8:50
  • 3
    Update to my previous comment: After reading Gilles' reference link, do not parse the output of ls, I've found that my find command was lacking. An arg was in the wrong place, and I've added null file-name endings. It is a bit long of a single line, but that's all I can do in a comment. Here is the fixed snippet: find . -maxdepth 1 -type f \( ! -iname ".*" \) -print0 | while read -rd $'\0' file ; do mv -- "$file" /other/location/ ; done – Peter.O May 11 '11 at 12:31
  • @perer Just as a note that the read -d option is not portable to all shells, but if you are using bash anyways, -d '' should get you the same effect as -d $'\0'. – jw013 Dec 26 '11 at 22:59

It's easiest in zsh:

mv -- *([1,100]) /other/location/

This moves the first 100 non-hidden files (of any type, change ([1,100]) to (.[1,100]) for regular files only, or (^/[1,100]) for any type but directory) in name lexicographic order. You can select a different sort order with the o glob qualifier, e.g. to move the 100 oldest files:

mv -- *(Om[1,100]) /other/location/

With other shells, you can do it in a loop with an early exit.

for x in *; do
  if [ "$i" = 100 ]; then break; fi
  mv -- "$x" /other/location/

Another portable way would be to build the list of files and remove all but the last 100.

  • +1 for safe shell expansion. Would also be more readable with the increment operation $(( i++ )) or $[ i++ ]? – user13742 Jan 16 '12 at 12:46
  • 2
    @hesse Some shells don't implement ++ and --. You can write : $((i+=1)) instead of i=$((i+1)); I'm not convinced that it's more readable. – Gilles Jan 16 '12 at 18:18
  • 1
    :-D, I actually edited this answer thinking it was mine... Sorry. Feel free to revert as that changes the meaning. – Stéphane Chazelas Jan 20 '15 at 18:08
  • @StéphaneChazelas I do wonder why you'd exclude directories and symlinks, the question said nothing about that. – Gilles Jan 20 '15 at 19:02
  • @Gilles, the accepted answer has ls -p | grep -v / so has the recent question that dups here. – Stéphane Chazelas Jan 20 '15 at 19:24

If you're not using zsh:

set -- *
[ "$#" -le 100 ] || shift "$(($# - 100))"
mv -- "$@" /target/dir

Would move the last (in alphabetical order) 100 ones.

The following oneliner in shell would help.

 foreach i (`find Source_Directory -type f --max-depth 1|tail -100`); do; {mv $i Target_Directory}; done
  • 1
    What's that shell? – phk Oct 28 '16 at 23:19
  • @phk, that would happen to work in zsh even if at first sight that looks quite alien to zsh syntax. Gilles has shown a much simpler way to do it in zsh. Even then, that's still more reliable than the currently accepted answer. – Stéphane Chazelas Sep 5 at 22:32

mmv is an outstanding utility which will also allow you to do mass renaming of files. (I had to sudo apt-get install mmv on my computer to install it.) Simple usage example: suppose you have a directory of files with extension .JPG that you'd like to change to a lowercase .jpg. The following command does the trick:

mmv \*.JPG \#1.jpg

The backslash is used to show a wildcard is coming up. The */JPG matches anything with a JPG extension. In the "to" portion of the command, the #1 uses the matching text from the first wildcard to rename the file. Of course, you can put a different path before the #1 to also move the file.

  • 2
    It would be more beneficial if you provided how you would actually use the tool you suggest to accomplish the goal. – Dason Dec 30 '11 at 5:55
  • 1
    added a usage example – Pete Dec 31 '11 at 2:25

The following worked for me. Sorry if it was posted previously, but I did not see it in a quick scan.

ls path/to/dir/containing/files/* | head -100 | xargs -I{} cp {} /Path/to/new/dir
c=1; d=1; mkdir -p NEWDIR_${d}
for jpg_file in *.jpg
if [ $c -eq 100 ]
d=$(( d + 1 )); c=0; mkdir -p NEWDIR_${d}
mv "$jpg_file" NEWDIR_${d}/
c=$(( c + 1 ))

try this code

Try this:

find /source/directory -type f -maxdepth 1 -print | tail -100 | xargs -J % mv % /other/location/
  • This is incorrect, you're passing three arguments to mv, the last one of which (probably) isn't a directory. And it doesn't really answer the question - the asker wants to move a given number of files, not all of them. – Mat Dec 30 '11 at 9:13
  • Command updated. – Saumil Jan 5 '12 at 8:37

I came by here, but I was needing to copy files in parts (99 each) from /DIR1 to /DIR2. I'll paste the script here to help otherz maybe:

# Thanks to <Jordan_U> @ #ubuntu
# 06 Dec 2014


for file in /DIR1/*; do
  cp "$file" /DIR2
  if [[ "$i" -ge "$copy_unit" ]]; then
    echo "Pausing, press enter to continue"

the following command works, if you are interested in using ls

$ ls -rt source/* | head -n100 | xargs cp -t destination

How does this work ??

  • ls -rt source/* - command lists all the files with the relative path
  • head -n100 - takes first 100 files
  • xargs cp -t destination - moves these files into the destination folder

If you want to be safe / handle filenames with spaces, newlines, quotes, backslashes etc. in them, you have to use null-terminated separators:

find "$srcdir" -maxdepth 1 -type f -print0 | head -z -n 100 | xargs -0 -r -- mv -t "$destdir" --

EDIT2: NOTE: if you don't have head -z (for whatever reason) you can replace the above head -z -n 1000 with tr '\0\n' '\n\0' | head -n 1000 | tr '\0\n' '\n\0' (or see other ways)

-maxdepth 1 will avoid looking for files in subdirectories of $srcdir, so the only ones listed are the files within $srcdir.
-print0 will use \0 instead of newline(\n) between each listed file - this helps handle files containing newlines and spaces with xargs.
head -z will count \0 terminated (instead of newline(\n) terminated) lines as lines. -n 100 will list only the first 100 files that find found.
If you want to see what command xargs will execute, add -t (or --verbose).
xargs -0 "Input items are terminated by a null (\0) character instead of by whitespace, and the quotes and backslash are not special (every character is taken literally)"
xargs -r will not run mv if there are no files to be moved (ie. if find did not find any files).
-- terminates processing of arguments as options to the program, more details here

Sample output (runs one mv command and can handle files with newlines in their name too):

$ find /tmp/t -maxdepth 1 -type f -print0 | head -z -n 100 | xargs -t -0 -r -- mv -t /tmp -- ; echo "exit codes: ${PIPESTATUS[@]}"
mv -t /tmp -- /tmp/t/file containing quotes"' then spaces /tmp/t/file containing quotes"' /tmp/t/file containing a slash n here\n /tmp/t/file containing a new line here
and continues /tmp/t/s /tmp/t/-x and -L 1. /tmp/t/of replace-str in the initi /tmp/t/-thisfile_starts_with_a_hyphen and has spaces and a -hyphen here /tmp/t/-thisfile_starts_with_a_hyphen and has spaces /tmp/t/-thisfile_starts_with_a_hyphen /tmp/t/another      with       spaces /tmp/t/one with spaces /tmp/t/c /tmp/t/a 
exit codes: 0 0 0

$ ls -1R /tmp/t
'another      with       spaces'
'file containing a new line here'$'\n''and continues'
'file containing a slash n here\n'
'file containing quotes"'\'''
'file containing quotes"'\'' then spaces'
'of replace-str in the initi'
'one with spaces'
'some dir'
'-thisfile_starts_with_a_hyphen and has spaces'
'-thisfile_starts_with_a_hyphen and has spaces and a -hyphen here'
'-x and -L 1.'

'file with spaces'

'/tmp/t/some dir':
'some file'

For find:

-maxdepth levels
       Descend at most levels (a non-negative integer) levels of direc‐
       tories below the starting-points.  -maxdepth 0
        means only apply the tests and actions to  the  starting-points
-type c
       File is of type c:

       b      block (buffered) special

       c      character (unbuffered) special

       d      directory

       p      named pipe (FIFO)

       f      regular file

       l      symbolic link; this is never true if the -L option or the
              -follow  option is in effect, unless the symbolic link is
              broken.  If you want to search for symbolic links when -L
              is in effect, use -xtype.

       s      socket

       D      door (Solaris)
-P     Never follow symbolic links.  This  is  the  default  behaviour.
       When find examines or prints information a file, and the file is
       a symbolic link, the information used shall be  taken  from  the
       properties of the symbolic link itself.
-L     Follow symbolic links.  When find examines or prints information
       about files, the information used shall be taken from the  prop‐
       erties  of  the file to which the link points, not from the link
       itself (unless it is a broken symbolic link or find is unable to
       examine  the file to which the link points).  Use of this option
       implies -noleaf.  If you later use the -P option,  -noleaf  will
       still  be  in  effect.   If -L is in effect and find discovers a
       symbolic link to a subdirectory during its search, the subdirec‐
       tory pointed to by the symbolic link will be searched.

       When the -L option is in effect, the -type predicate will always
       match against the type of the file that a symbolic  link  points
       to rather than the link itself (unless the symbolic link is bro‐
       ken).  Actions that can cause symbolic links  to  become  broken
       while  find  is executing (for example -delete) can give rise to
       confusing behaviour.  Using -L causes  the  -lname  and  -ilname
       predicates always to return false.

For head:

-n, --lines=[-]NUM
       print the first NUM lines instead of  the  first  10;  with  the
       leading '-', print all but the last NUM lines of each file
-z, --zero-terminated
       line delimiter is NUL, not newline

EDIT: Someone mentioned that they didn't have head -z, this is the version that I was using(in Fedora 25):

$ head --version
head (GNU coreutils) 8.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie and Jim Meyering.

$ rpm -qf /usr/bin/head

For xargs:

-0, --null
       Input  items  are  terminated  by a null character instead of by
       whitespace, and the quotes and backslash are not special  (every
       character is taken literally).  Disables the end of file string,
       which is treated like any other  argument.   Useful  when  input
       items  might  contain  white space, quote marks, or backslashes.
       The GNU find -print0 option produces  input  suitable  for  this
-r, --no-run-if-empty
       If the standard input does not contain any nonblanks, do not run
       the command.  Normally, the command is run once even if there is
       no input.  This option is a GNU extension.
-P max-procs, --max-procs=max-procs
       Run  up  to max-procs processes at a time; the default is 1.  If
       max-procs is 0, xargs will run as many processes as possible  at
       a  time.   Use the -n option or the -L option with -P; otherwise
       chances are that only one exec will be  done.   While  xargs  is
       running,  you  can send its process a SIGUSR1 signal to increase
       the number of commands to run simultaneously, or  a  SIGUSR2  to
       decrease  the number.  You cannot increase it above an implemen‐
       tation-defined limit (which is shown with  --show-limits).   You
       cannot  decrease  it  below  1.  xargs never terminates its com‐
       mands; when asked to decrease, it merely waits for more than one
       existing command to terminate before starting another.

       Please  note  that  it is up to the called processes to properly
       manage parallel access to shared  resources.   For  example,  if
       more  than one of them tries to print to stdout, the ouptut will
       be produced in an indeterminate order (and very likely mixed up)
       unless  the  processes  collaborate in some way to prevent this.
       Using some kind of locking scheme is one  way  to  prevent  such
       problems.   In  general, using a locking scheme will help ensure
       correct output but reduce performance.  If  you  don't  want  to
       tolerate  the  performance  difference,  simply arrange for each
       process to produce a separate output file (or otherwise use sep‐
       arate resources).
-t, --verbose
       Print  the command line on the standard error output before exe‐
       cuting it.

For cp:

-t, --target-directory=DIRECTORY
       copy all SOURCE arguments into DIRECTORY
-v, --verbose
       explain what is being done

I know this thread is a pretty old, but I found the answers more complicated than I thought they should be. This worked in CentOS, but it seems simple enough that it should probably work in other distros.

cp `ls someDir | head -n 100` someDir100/
  • 1
    That doesn't work because the output of ls won't include the leading somedir/ prefix, and won't work for filename with blank or wildcard characters or start with -. – Stéphane Chazelas Nov 28 '12 at 14:38
  • Fair enough. I actually did cp ls | head -n 100 ../someDir100/ From inside the target directory and none of the file names satisfied those cases. Better to be lucky then good! – Jason Nov 28 '12 at 15:20

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.