Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a ton of files and dirs in a subdirectory I want to move to the parent directory. There are already some files and dirs in the target directory which need to be overwritten. Files that are only present in the target should be left untouched. Can I force mvto do that? It (mv * ..) complains

mv: cannot move `xyz' to `../xyz': Directory not empty

What am I missing?

share|improve this question
    
Have you tried mv -f? – ierax Mar 22 '11 at 17:16
1  
Ofcourse....... – EricSchaefer Mar 22 '11 at 17:44
up vote 50 down vote accepted

You will have to copy them to the destination and then delete the source, using the commands cp -r * .. followed by rm -rf *.

I don't think you can "merge" directories using mv.

share|improve this answer
1  
Well, that's what I didn't want to do, because it will take a long time... Thanks anyway. – EricSchaefer Mar 22 '11 at 17:45
9  
Presumably mv is faster because you're on the same filesystem? What if you use cp -l to create hardlinks rather than actually moving the files? – mattdm Mar 22 '11 at 20:32
3  
You should use cp -a instead of cp -r in order to preserve the file attributes (timestamp, permissions, etc.). – dotancohen Feb 2 '14 at 7:14
    
For people arriving here late via google, the answer below by @palswim emulates the behavior of mv by creating new hard links to the data and then deleting the old links. Short answer cp -rl source destination && rm -r source. – William Everett May 31 at 17:43

rsync would probably be a better option here. It's as simple as rsync -a subdir/ ./.

My test tree in filename:contents format:

./file1:root
./file2:root
./dir/file3:dir
./dir/file4:dir
./subdir/dir/file3:subdir
./subdir/file1:subdir

Running rsync:

$ rsync -a -v subdir/ ./
sending incremental file list
./
file1
dir/
dir/file3

Gives:

./file1:subdir
./file2:root
./dir/file3:subdir
./dir/file4:dir
./subdir/dir/file3:subdir
./subdir/file1:subdir

And then, to emulate mv, you probably want to remove the source directory:

$ rm -r subdir/

Giving:

./file1:subdir
./file2:parent
./dir/file3:subdir
./dir/file4:dir

If this is wrong, can you please provide a similar example (e.g. using my test tree from near the top of this answer) with the desired result?

share|improve this answer
    
rsync copies. This question is about moving. – Gilles Mar 22 '11 at 22:51
1  
@Gilles: Thanks. I added rm -r at the end to make it basically the same as mv. – Mikel Mar 22 '11 at 22:53
1  
copy-then-delete isn't equivalent to mv when the source and destination are on the same filesystem. mv is atomic, preserves inode numbers (so the file can remain open), and doesn't take time and space making a copy. – Gilles Mar 22 '11 at 23:08
5  
@Gilles: I realize that, but currently the leading answer is cp -r; rm -r. I think in that sense, rsync is worth mentioning too. – Mikel Mar 22 '11 at 23:21
    
I already did it with cp/rm (it was urgent). It really took a long time. Gilles script would probably have been a lot quicker, but he was too late too. – EricSchaefer Mar 23 '11 at 10:09

rsync can delete the source after copies with the --remove-source-files parameter. This should be a convenient way to do what you'd like.

From the rsync man page:

        --remove-source-files   sender removes synchronized files (non-dir)
share|improve this answer
    
This is really the best answer. I couldn't use cp -r; rm because of lack of free space. Instead rsync --remove-source-files both minimized used disk space avoided copying over the exact same files. – Kasper Souren Aug 5 '14 at 12:10

Here's a script that moves files from under /path/to/source/root to the corresponding path under /path/to/destination/root.

  • If a directory exists in both the source and the destination, the contents are moved-and-merged recursively.
  • If a file or directory exists in the source but not in the destination, it is moved.
  • Any file or directory that already exists in the destination is left behind. (In particular merged directories are left behind in the source. This is not easy to fix.)

Beware, untested code.

export dest='/path/to/destination/root'
cd /path/to/source/root
find . -type d \( -exec sh -c '[ -d "$dest/$0" ]' \; -o \
                  -exec sh -c 'mv "$0" "$dest/$0"' {} \; -prune \) \
    -o -exec sh -c '
        if ! [ -e "$dest/$0" ]; then
          mv -f "$0" "$dest/$0"
        fi
' {} \;
share|improve this answer
    
Two corrections: you need a \; before the -o on the first line of the find command, and you shouldn't escape ! in the if -- it's just !, not \! – llhuii Apr 20 '11 at 5:30

You can do this with cp and rm, but without copying the massive amount of data you are (presumably) trying to avoid transferring. @mattdm alluded to this in his comment, and an answer for another question has a more complete discussion about various options.

cp -rl source destination
rm -r source

Essentially, the -l option for the cp command creates hard links to files rather than copying their data to new files.

share|improve this answer
1  
I know the OP already completed his task which prompted the question, but hopefully this answer can help anyone with this problem in the future. – palswim Jan 31 '15 at 7:36
    
This really the answer they needed. I just did this with 60GB of thousands of small cyrus email files and it took only 21 seconds. – labradort May 12 '15 at 18:37
    
This is also the route I took - I just changed it to cp -al source destination to preserve owner info and permissions. – piit79 Nov 20 '15 at 9:32

This thread is out there for years and still ranks #1 on google so i wanted to add another method. How i usually do this: packing the subdir content into a tarball, moving the tarball up to the parent directory and then extract it with the default --overwrite behaviour. This does exactly what you're looking for. Afterwards you can remove your subdir.

cd xyz
tar -cvzpf tmp.tar.gz *
mv tmp.tar.gz ../tmp.tar.gz
cd ..
tar -xvzpf tmp.tar.gz
rm -rf xyz
rm -f tmp.tar.gz
share|improve this answer
    
This only works if you have the extra space for the compressed tar file. And do you really want to keep the temporary tar file around after extraction? – Anthon Apr 13 at 9:05
    
Edited code to remove tmp file. Nowadays the space isn't the problem in the most cases. #terabyteages – Simon Kraus Apr 13 at 9:22

If you have enough storage you can do it the following way:

mv -bfv directory_1/* directory_2/ # all duplicate source files/directories 
                                   # will have ~ appended to them
find -name "*~" -delete            # will recursively find and delete all files 
                                   # with ~ on the end

Make sure there aren't any important files with a ~ on the end of them, but if there are you can add --suffix=whateveryouwant instead of the default.

share|improve this answer

I find the easiest way is to just pipe yes to the cp command like this:

yes | cp -R /source/* /destination/
share|improve this answer
4  
What on earth does yes add here? – Bernhard Mar 24 '14 at 6:21

I just used kind of the same as last one. Without any yes |.. I had a problem which needed overwriting some files over ssh after decompression. What I did was

cp -R * ..

share|improve this answer

protected by Anthon Apr 13 at 9:05

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

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