Gradual slowing of large SMB file transfer

[jmcguire525]

Server Specs: E5-2683v3, 64GB DDR4 Ram, 6x8TB Raid Z2, FN 11.1
W10 Computer Specs: i5 6600k, 16GB DDR4 Ram, Seagate 4TB usb 3.0 External Drive

I tried out an NFS share and could only manage 60MBps transfer speeds with the W10 NFS client, then did some tests with SMB and was getting 112MBps. To test out a large transfer I decided to move a bunch of football games I had recorded over my network and for over an hour it stayed right at 112MBps...

When I came back later to check on things I saw that the transfer has been steadily slowing down and is nearly half of that speed with all indications that it is going to continue to slow. Any guesses as to why this is happening? All of the files are relatively similar in size.

 

[toyebox]

To rule out the USB 3.0 drive, do you have the available space to try copying to a local internal drive?

Would you mind listing your FreeNAS version info and any specific tunables or non standard changes that may have been made?

 

[jmcguire525]

I don't have room on the internal drive. Freenas 11.1 without any tunables or changes made. I now have two transfers going on from two USB 3.0 drives and the combined write speed is 112MBps. Still seems odd that the first transfer slowed after writing at 112MBps for over an hour, but that does seem to be a drive issue now that the other transfer has saturated the connection.

 

[anodos]

Post contents of /usr/local/etc/smb4.conf and /var/log/samba4/log.smbd. <or attach the files>

 

[olsenblane]

I am having the exact same issue. Here are the contents of the logs @anodos requested from OP.
The log file you requested was too large to attach, but here are two error that repeatedly showed up in the log:

[2017/09/17 17:04:46.964942, 1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter)
WARNING: The "null passwords" option is deprecated

[2017/06/09 21:48:54.168628, 0] ../source3/lib/util_sock.c:1055(get_remote_hostname)
matchname failed on 192.168.10.20

What is interesting about the second error (matchname failed), is that I see an entry in Windows Event log after the transfer fails about similar issue. This is across multiple computers (all happen to be Windows 10, but from the forums, even MAC users are having this issue).