Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Copy from one share to another...

Featured Replies

  • Community Expert

Hello -

 

I just a had a curious question. I noticed that the speed of copy/move command depended on the SMB client computer I used to issue the command even though the move was happening within 2 disks of the server - why is that?

 

Here is the scenario - I created a new share and was moving some of my existing files in the server from the old a share to the new share. I cut and pasted the file folder from a Wirelessly connected laptop and the whole process in Teracopy showed to be almost 6 hours long. (OS - Win 10 64 bit)

 

I cancelled that operation and came to my wired desktop (Gigabit ethernet connection to the router - same as the Tower) and did the same cut/paste operation for the same amount of data and it showed about 19 minutes in teracopy and completed within about 25 minutes. (OS - Win 10 64 bit)

 

So that was the basis of my question - now I understand that a gigabit wired connection is faster/better than a wireless connection any day but as I understand that should not matter in this case since both the source and destination of the move is located within the server - only the command is issued from a SMB client - why would the speed depend on the client since the move was internal. Would this be significantly faster if I used the command line (via telnet -putty) instead of the SMB clients?

 

I might be missing something very elementary here - apologize if that is the case - not trying to waste anybody's time. Just wanted know for my own good. Thanks

Hello -

 

I just a had a curious question. I noticed that the speed of copy/move command depended on the SMB client computer I used to issue the command even though the move was happening within 2 disks of the server - why is that?

 

Here is the scenario - I created a new share and was moving some of my existing files in the server from the old a share to the new share. I cut and pasted the file folder from a Wirelessly connected laptop and the whole process in Teracopy showed to be almost 6 hours long. (OS - Win 10 64 bit)

 

I cancelled that operation and came to my wired desktop (Gigabit ethernet connection to the router - same as the Tower) and did the same cut/paste operation for the same amount of data and it showed about 19 minutes in teracopy and completed within about 25 minutes. (OS - Win 10 64 bit)

 

So that was the basis of my question - now I understand that a gigabit wired connection is faster/better than a wireless connection any day but as I understand that should not matter in this case since both the source and destination of the move is located within the server - only the command is issued from a SMB client - why would the speed depend on the client since the move was internal. Would this be significantly faster if I used the command line (via telnet -putty) instead of the SMB clients?

 

I might be missing something very elementary here - apologize if that is the case - not trying to waste anybody's time. Just wanted know for my own good. Thanks

 

When you copy between shares on smb, what you're actually doing is copying from the source share to the destination share via the smb client....

 

If you need to copy between shares then you're far better off doing that either through cmd line, using midnight commander (mc from a cmd prompt) or by using the dolphin or krusader docker containers.

  • Author
  • Community Expert

Thank you CHBMB!

 

Appreciate the explanation and the suggestions.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.