NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN104 - Really Slow Copy Speeds
Hey guys, I'm copying a share from one volume to a new volume through SSH using MC (Midnight Commander) and I'm getting an avg of 6.33MB/s. Going to take 35mins or so to copy 14GB.
I know this...
WiredRacing wrote:
minidlnad is using about 70% of the memory, but not much cpu.
You could try disabling the DLNA service and see if that makes any difference.
The 'minidlnad' processed eventually dropped off 'top' and went down to sub 6%. Though curiously the amount of memory in use stayed the same.
When my SMB copy stopped, I stopped readynasd (as it was always trying to take up 100% of the cpu) and then started it and it started to behave "normally" (only spiking when using the management console). However, I tried another copy within midnight commander, large file, and it still didn't go over 10mb/s while the SMB copy with readynasd under control and no other backup process happening would top out in the mid 50's (generally hanging around in the mid 40's). smbd around migh 50 to mid 60% cpu, which kicks up kswapd0 to low teens. 3 kworker processes, usually 2 of them equal 10%.
When I sort 'top' by mem%, 'minidlnad' it's the highest (at 5.6%) but no other process seems to be using a lot of memory despite 480000 used and only ~30000 free. The swap looks much better now though, only 10,416 used. 3-5 running tasks, 187(!) sleeping (0 stopped or zombie).
So yeah this is still quite odd why smb copies so much faster. Haven't rebooted yet, ALMOST done migrating all my data over. Just a few more hours now.
So, after powering down. Moving my new drive that I was copying all this data to into another slot, turning it back on. Then shutting down again and reinstalling an exported 2-disk volume, turning it back on to verify it worked. Then exporting it again, removing it. Putting two other disks in, creating a RAID 0 volume of those and manually editing smb.conf (which was not loading due to "smb encryption = (null)"). I created some backup jobs to backup data from the Bay 1 drive to this new array and I'mgetting an avg of 44mb/s through the management console and using the backup jobs.
So it appears, somewhere in that process, part of my problem(s) corrected themselves.
Once the backups are done, I'll run the various commands and tests mentioned here and post the results for future reference.
Going to probably need to start another thread on the SMB config issue because as soon as I reboot, it will overwrite my change, so somewhere else in the system is some thing else that needs to change, or I need help to write a script to update and re-try 'systemctl start smb' after a minute or two after booting. Anyhow, separate issue (but part of the odyssey of this single drive upgrade project).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
