[SOLVED] SAMBA with big files

[russian]

Hi.

I've got some problem with big data transfer via SAMBA.

It doesn't matter, if it just copying, or it's some file handling (e.g. MKVtoolNix file handling).

I have Windows7 as my main PC, and Nas4Free as my NAS.

Firstly SAMBA had NT1 as "Max protocol" at SAMBA/CIFS settings.

And in the error moment log had such records:

Nov 10 22:11:30 nas4free smbd[57746]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_IO_TIMEOUT.
Nov 10 22:11:30 nas4free smbd[57746]: [2012/11/10 22:11:30.525537, 0] smbd/process.c:244(read_packet_remainder)
Nov 10 21:52:11 nas4free smbd[44393]: send_file_readX: sendfile failed for file ***HERE IS FILE NAME*** (Broken pipe). Terminating
Nov 10 21:52:11 nas4free smbd[44393]: [2012/11/10 21:52:11.985532, 0] smbd/reply.c:3618(send_file_readX)

Then I set "Max protocol" to SMB2, coz I have Windows7. And now errors recorded in such way:

Nov 10 22:56:20 nas4free smbd[58454]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_IO_TIMEOUT.
Nov 10 22:56:20 nas4free smbd[58454]: [2012/11/10 22:56:20.795566, 0] smbd/process.c:244(read_packet_remainder)
Nov 10 22:54:59 nas4free smbd[58304]: read_fd_with_timeout failed for client 0.0.0.0 read error = NT_STATUS_CONNECTION_RESET.
Nov 10 22:54:59 nas4free smbd[58304]: [2012/11/10 22:54:59.296212, 0] smbd/process.c:244(read_packet_remainder)

All my SAMBA/CIFS settings are here:





Where should I search the problem, how do u think?

Thanx.

[alexey123]

Check transfer with XP. As for me, 4G disk image transfered many times without any problems.
without service pack 3 Windows not working

[russian]

My suspicious about SAMBA problem was fault. I have some at DMESG output at the moment of fault:

re0: link state changed to DOWN
re0: link state changed to UP

So, it's not SAMBA problem. It's an interface problem (don't know, hard or soft).

[alexey123]

If your sambaclient broke tcp buffer during transfer, network card make reset ?

[HotBlack]

Hello,

Just upgraded from FreeNAS 7. Evrything is working fine.... except this

I am getting the same error; when copying a file to/from a windows 7 or a windows 8 client. of size >10MB the copy fails. Specifically windows 8 reports this error: 0x8007003b.

Has anybody found a solution?

[raulfg3]

Your NIC is Realtek 8111E I'm not totally sure because is not clear, but there are some other post relating problems with this NIC.

Please try other diferent NIC, perhaps Intel based NIC to discard problem in the re0 driver.

PD: Do you have McAfee on your win 7 or win 8 PC? = http://serverfault.com/questions/292784 ... -dfs-share

[HotBlack]

Ok, I seem to have found a fix. The problem seems to be with SMB signing:

When SMB signing is enabled on both the client and server, SMB sessions are authenticated between the machines on a packet by packet basis. This does have a performance hit of between 10 to 15% as every packet's signature has to be verified.

I disabled SMB signing on my win 7 and 8 clients. By setting the values of the registry keys: EnableSecuritySignature and RequireSecuritySignature to 0 (zero) in the the following registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

This worked for me. I believe you can switch of SMB signing on the server side instead by passing an extra parameter to the SMB daemon, but I could not find a parameter which worked.

(I am on an Intel NIC)

[russian]

Btw, as topic starter, i want to say, that my problem is solved.

I did 2 things, but I don't know which of them was the reason of success:

1. I've set "Enable Asynchronous I/O"

2. I found that MTU on my NAS NIC was set to very big value (9014), but I know that my router couldn't work with MTU more than 1450 or something about it. So, I've found the maximum possible MTU (by pinging my windows comp from NAS with command ping -D -s <MTU size> <WinCompIp>) and set it on NAS with command ipconfig <NIC> MTU <MTU size>

After I've done it, my copying and working with big files was done without any problem.

Hope, it could be usefull for somebody else.

[onur]

Btw, as topic starter, i want to say, that my problem is solved.

I did 2 things, but I don't know which of them was the reason of success:

1. I've set "Enable Asynchronous I/O"

2. I found that MTU on my NAS NIC was set to very big value (9014), but I know that my router couldn't work with MTU more than 1450 or something about it. So, I've found the maximum possible MTU (by pinging my windows comp from NAS with command ping -D -s <MTU size> <WinCompIp>) and set it on NAS with command ipconfig <NIC> MTU <MTU size>

After I've done it, my copying and working with big files was done without any problem.

Hope, it could be usefull for somebody else.

I had the same problem with Windows 8 and NAS4FREE. This method worked for me. Thank you.