OK, so following the help I used the command:

 

mv /Mnt/Disk3* /mnt/Disk5

 

Disk3 started with a movies directory with everything in it.  Disk5 started with a Movies directory in it and everything under it.  I expected the movies directory on drive 3 to move to disk 5.  Instead I ended up with a directory disk3/Movies on disk 5.

 

Hmm...  OK, so:

 

1) What was the correct syntax?

2) How do I stop the copy that is moving merrily along

3) What is the correct syntax to now move all of /disk5/disk3/Movies to /Disk5/Movies and get rid of the empty /disk3 directory on disk 5 when the move finishes.

 

TIA for your assistance.

 

jwcolby

 

 

I think you can do it all from a Windows Explorer window. If you navigate to \\tower\diskx, then you'll see the actual disk share. If you move disk5\disk3\movies to disk5\movies, it should stick. Next time, you can just do a move or copy from disk share to disk share, if, like me you're not that great on the command line.

1) What was the correct syntax?

HEHE, you forgot a "/"  it was not "Disk3*" it should have been "disk3/*"

 

2) How do I stop the copy that is moving merrily along

I would not do that.  You are in the middle of a move (mv) operation and not a copy.  I am not sure what might happen if you cancel the move.

 

3) What is the correct syntax to now move all of /disk5/disk3/Movies to /Disk5/Movies and get rid of the empty /disk3 directory on disk 5 when the move finishes.

Do a google search of "man mv" and see what pops up.  You can us the mv command to do what you need to.  If you still have questions post back here and we can confirm the command for you.

I think you can do it all from a Windows Explorer window. If you navigate to \\tower\diskx, then you'll see the actual disk share. If you move disk5\disk3\movies to disk5\movies, it should stick. Next time, you can just do a move or copy from disk share to disk share, if, like me you're not that great on the command line.

 

If you use explorer it moves the files across the network.  I am trying to do this from disk to disk right inside of Tower (Linux).

 

jwcolby

I started the move again but while the target free space (as reported by Tower/Main) is decreasing, the source free space is not increasing.  It appears that I am doing a copy.  However I am using Mv.

 

jwcolby

I started the move again but while the target free space (as reported by Tower/Main) is decreasing, the source free space is not increasing.  It appears that I am doing a copy.  However I am using Mv.

 

jwcolby

"mv" will not remove the source file until the target file is completed.  Therefore, the source file-system will not show the decrease until the mv command advances to the next file.

In effect you are performing a copy to the target disk followed by a remove of the source file.

I started the move again but while the target free space (as reported by Tower/Main) is decreasing, the source free space is not increasing.  It appears that I am doing a copy.  However I am using Mv.

 

jwcolby

"mv" will not remove the source file until the target file is completed.  Therefore, the source file-system will not show the decrease until the mv command advances to the next file.

In effect you are performing a copy to the target disk followed by a remove of the source file.

 

Unless you are saying that it will not remove the source until all files in the subdirectory are moved, then something else is going on.  I am moving my Movies directory.  Underneath that are subdirectories with the actual movie files.  I have been doing this for hours and the destination drive free space is steadily decreasing but the source drive free space is not increasing.  Now if Mv is waiting until it copies all of the subdirectories before it deletes any source files then this makes sense.  Essentially whenever everything is moved, everything in the source Movies directory will be deleted simultaneously.  I was expecting to see the source free space increase after each individual file is moved, regardless of where that file is physically stored.