NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Moves on new NAS much slower than old NAS
Greetings, I recently had a power supply failure on my old OS4 ReadyNAS Pro Pioneer RNDP600E and migrated my data to a ReadyNAS 626X RN626X00. It is connected to my Windows 10 computer via 10GbE as ...
If you are moving between shares, OS-6 will do a copy-delete (due to the fact that the two shares are different BTRFS subvolumes). You can get faster speeds when mapping the entire data volume, and not just a share. Then it will usually do a true move, even across shares.
You can also get faster speeds by disabling "strict sync" in the advanced SMB settings for the share. Though some applications might misbehave when you do that.
I assume you were still on OS4.2.x on the Ultra. What you are experiencing, as StephenB explained, is one of the differences caused by the BTRFS file system OS6 uses. This one can seem to be a negative, but there are also lots of positives. Shares are BTRFS sub-volumes, not just directories. You may want to re-think your share structure because of it. Unless you really need separate access control, make what was separate shares into directories within a share. Moving between directories within a share is still just as fast as with the EXT4 file system of OS4. From SSH, you can also use the cp command with the --reflink option to just copy the pointer to the file to a new share/directory, then delete the original, which is also much faster than copying the whole file. You probably won't want to do that all the time, but it can be useful when doing the initial housekeeping after moving to an OS6 system.
Hi,
"You can get faster speeds when mapping the entire data volume, and not just a share. Then it will usually do a true move, even across shares."
As you have suggested, I tried mapping the entire volume, in my case this is called c, for example:
\\NAS_NETWORK_NAME\c
When moving files or folders between subdirectory shares under c, a copy/delete still occurs.
For example, if moving the contents of:
\\NAS_NETWORK_NAME\c\Music\
to:
\\NAS_NETWORK_NAME\c\Videos\
It seems that I am still misunderstanding something. Am I mapping the entire data volume incorrectly by mapping \\NAS_NETWORK_NAME\VOLUME_NAME ?
Thanks for your help!
Crash_HI wrote:
\\NAS_NETWORK_NAME\VOLUME_NAME ?
That is the correct path, though you do need to use the NAS admin credentials.
I wasn't sure if you were doing this on the OS-6 NAS, since the default volume name there is data, not C.
AFAIK, mapping the whole volume will help some, as the NAS will then do the mv as a copy/delete entirely internally rather than the PC doing a bucket-brigade over Ethernet. But even from SSH, I have not seen that a mv will automatically use the --reflink option for the copy part. The explanations I've seen as to why this is the default behavior in BTRFS vary, but the one that seems to make the most sense is that if you run out of metadata space while the cp is happening, the kernel doesn't know it and goes ahead with the rm, resulting in data loss.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
