[SOLVED] moving top level directory after disk copy

[Brucey7]

I am in the middle of converting to XFS, after rsync --progress -avh /mnt/disk3/ /mnt/disk14/ completed succesfully, I moved disk 14 into disk3 slot, changed the assignment in the main page and started the array

 

disk3 folder structure now starts with top level directory disk3 and my user share of HD Movies under that.

 

When I map a disk share to disk3 it shows the top level directory as HD movies, however when I browse it from the webgui, the top level directory is disk3.

 

The files in disk3's HD Movies are no longer being included in my HD movies share, how do I get to the real top level directory to move HD movies back up to the top level?

 

[Brucey7]

I should add, since there is another rsync command running, i prefer not to stop the array, alternatively, I'll have to leave it 44 hours for the next disk copy (6TB) to finish

[trurl]

So are you saying you have /mnt/disk3/disk3/HD Movies?

 

What you want to do is very easy (and easy to figure out) in mc (Midnight Commander). Have you ever used it?

 

[Brucey7]

Yes I have  have /mnt/disk3/disk3/HD Movies. 

 

I have never used midnight commander, I looked at it once but it seemed to destroy the formatting on my screen.

 

I would have thought mapping a disk share would have shown me /disk3/HD Movies  but it only shows me /HD Movies

[Brucey7]

I fixed it at the CLI with the mv command

 

My MC doesn't draw or navigate properly, it looks like it's set up for the wrong kind of terminal device

[itimpi]

I fixed it at the CLI with the mv command

Glad to hear that it is sorted.

 

Note that the initial problem was because of a trailing slash in the rsync command that resulted in an extra directory level being created when moving files.  You will need to look at the rsync documentation to see what effect trailing slashes have on path (on the assumption I=you did not deliberately create this extra level).

 

My MC doesn't draw or navigate properly, it looks like it's set up for the wrong kind of terminal device

You need to ensure the TERM environment variable is set correctly.  I cannot remember offhand what a valid value is for use with mc but it should be easy enough to find an appropriate thread in the forum.

[Brucey7]

Thank you very much for that, you are right, i prefer not to have the extra directory level, but I can live with it.  I added the trailing slash on the source because my rsync documentation says "A trailing slash on the source changes this behavior to avoid creating an additional directory level at the destination" (techonthenet.com), clearly it's not the case.  I guess I can try the next disk without the trailing slash.

 

The MC problem  could be because I run my servers headless and telnet across to them from a windows client, I did have a look at the terminal help in MC, but it's about as useful as a chocolate teapot.

[itimpi]

Thank you very much for that, you are right, i prefer not to have the extra directory level, but I can live with it.  I added the trailing slash on the source because my rsync documentation says "A trailing slash on the source changes this behavior to avoid creating an additional directory level at the destination" (techonthenet.com), clearly it's not the case.  I guess I can try the next disk without the trailing slash.

If you re going to have an extra directory level you do not want it to be called disk3 (or an equivalent) as that means you can end up with both a disk share and a User share with the same name which can lead to confusion when trying to view the contents.

 

The MC problem  could be because I run my servers headless and telnet across to them from a windows client, I did have a look at the terminal help in MC, but it's about as useful as a chocolate teapot.

So do I and have no problem.  I use puTTY and have the Windows->Translation->Remote Character set setting at UTF-8 and the Connection->Data->Terminal type string as 'xterm'.    This combination seems to work fine with mc.

[Brucey7]

I'll give it a go, thank you again