OK, I see the following thread has a bit more on this:
Are there any implications of moving files this way? I’m quite picky about preserving all the file metadata / datestamps etc as I migrate over time from one device to another. In particular, I want to preserve file creation and modification timestamps, because they hold valuable information in my view that mustn’t be lost in moving from one drive to another, or one folder to another.
Also, moving files in this way “by stealth” won’t confuse the drive controller’s view of what is stored, where? For example, even just using “mkdir” to creat a new share won’t mean that that new share isn’t visible to the drive’s web interface setup facility?
Borrowing from the above thread, can I just check that I’ve understood what I should do (not wanting to mess up), in moving everything (folders, files) from share existing “ShareA” to new “ShareB”…
(1) Go to http://yourIP/UI/ssh where yourIP is the IP address of the MyBook.
(2) Login as root, password welc0me (that’s a zero in there).
(3) cd /DataVolume/shares (change dir to where your shares are).
(4) ls (list your shares).
(5) mkdir ShareB (make a new folder for the new share).
(6) mv ShareA/* ShareB/ (move everything in ShareA into ShareB).
Another question: in step (5) above, if mkdir at the top level makes a new share, if you then cd (change directory) into that new share, and use mkdir again, will it just create a “normal” folder. There appears to be a big distinction with this drive between a share (which is like a complete separate partition) and a folder.
And another related question: if I am moving files/folders from ShareA into “ShareB\subfolder” (i.e. a subfolder within new ShareA, not at the top level), will the above method work, just using mkdir in step (5) to create the subfolder, and putting in the full path to the new subfolder in step (6). In other words:
(5*) mkdir ShareB (make a new folder for the new share).
(6*) cd ShareB
(7*) mkdir subfolder
(8*) cd /DataVolume/shares
(9*) mv ShareA/* ShareB/subfolder