This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I'm running the latest ReadyNAS 6.9.4hotfix1 on my ReadyNAS with more than 3.5 TByte free and a Windows 10 Pro x64 workstation and have for many years (with whatever the latest official version was at the time). They are both connected to a GBit full-duplex switch which consistently gives me (and has forever) the theoretical maximum file transfer speeds of 112 MByte/second or so.
Now I am trying to do something I've done literally thousands of times before and suddenly it fails consistently: Transferring large files from the workstation to the NAS. From Windows Explorer or cmd.exe, copying or moving a file works fine at full speed until it hits the 2 GByte point then it stops and errors out.
Transferring files between the same drives/filesystems from the NAS to the workstation continues to work regardless of size. The workstation file system is whatever the current NTFS is and the NAS of course runs btrfs.
Re: Cannot Copy Files Larger Than 2 GByte to ReadyNAS
That sounds weird, @CarlEdman. What happens in case you use the admin page in a browser on your windows workstation to pull (upload) one of the concerned files to the nas?
Re: Cannot Copy Files Larger Than 2 GByte to ReadyNAS
That sounds weird, @CarlEdman. What happens in case you use the admin page in a browser on your windows workstation to pull (upload) one of the concerned files to the nas?
For instance you could set up a 400 MB transfer test running 20 times (8 GB total) and see if that fails. Then adjust the file size upwards the the loop count downwards (800 MB x 10, 1000 MB*8, 2000 MB*4, 4000 MB *2, ...), until you find the failure point.
FWIW, I don't see how this would be related to ipv6, though I agree that you should disable ipv6 if you don't need it (and most people don't).
Re: Cannot Copy Files Larger Than 2 GByte to ReadyNAS
@StephenB wrote: "FWIW, I don't see how this would be related to ipv6, though I agree that you should disable ipv6 if you don't need it (and most people don't)."
You are most probably right, but my recommendation belongs to the category "Do not enable anything you do not truely need". As I think the issue is network related, disabling IPv6 will reduce the complexity of the network configuration. Even, if it might not be the solution, it might bring us closer to a situation, where we finally can identify the reason(s) for the issue.
Re: Cannot Copy Files Larger Than 2 GByte to ReadyNAS
Thanks for all the advice from @Retired_Member and @StephenB. To take the points in order:
1. The problem just disappeared as mysteriously as it appeared. Copying the same file 3.4 GByte from the same local directory to the same NAS directory suddenly worked as expected. No config changes, no reboots on either client or server. I have no idea why, but please believe me that I'm not the sort of ninny who runs to the forum without reproducing the issue at least half a dozen times, both from Windows explorer and cmd.exe.
2. I'd never tried NAS tester before, but I did as suggested and am quite pleased with the results: Pretty rock solid ~114 MByte/second real throughput read and write, close enough to the theoretical Gigabit Ethernet limit as to satisfy me. Details attached below.
3. I don't recall deliberately enabling IPv6 on my ReadyNAS, but if I read the configuration correctly, it is set to "Automatically/DHCP." Not that it matters as I don't expose the NAS to the outside world and there are only 100 to 200 devices on my home network (wired and wireless combined).
Re: Cannot Copy Files Larger Than 2 GByte to ReadyNAS
Great to hear, that you are fine now, @CarlEdman. You are not the only one, who experienced erratic behaviour from solutions, which were running stable for a long time. As there are so many components involved in delivering services, the slightest change in one element is sometimes causing hickups. For example I observed several "mysterious" issues on intel NUCs after applying windows driver updates, which just disappeared after a few days and never occurred again.
3. I don't recall deliberately enabling IPv6 on my ReadyNAS, but if I read the configuration correctly, it is set to "Automatically/DHCP." Not that it matters ...
In some cases Windows will use the ipv6 link local address to connect with the NAS. There are posts here from folks who say that they've seen lower performance when that happens. I believe in most of those cases ipv6 was disabled on the router.
I would still disable it if your home network is configured to use ipv4.
