To whom it may concern, I'm having some issues writing large files to my samba share. After about 11Gb it fails ( for the past three transfer attempts). The Files are sized between 2Gb and 65gb respectively I was getting Oplock errors so i disabled oplock but still have an issue. Below is the output hopefully someone knows what i am doing wrong. TIA Ed [2004/08/04 11:35:47, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:35:47, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:43:01, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13254) [2004/08/04 11:44:05, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:44:05, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [root@vegas samba]# tail -n 30 log.scgad2 [2004/08/04 10:56:53, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 10:56:53, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:08:03, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13250) [2004/08/04 11:10:19, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13250) [2004/08/04 11:32:08, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13253) [2004/08/04 11:32:09, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13253) [2004/08/04 11:32:19, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:32:19, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:33:38, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13254) [2004/08/04 11:35:47, 0] lib/util_sock.c:read_socket_data(367) read_socket_data: recv failure for 4. Error = Connection reset by peer [2004/08/04 11:35:47, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:35:47, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:43:01, 1] smbd/service.c:make_connection_snum(619) scgad2 (90.0.0.149) connect to service raid initially as user administrator (uid=100, gid=101) (pid 13254) [2004/08/04 11:44:05, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid [2004/08/04 11:44:05, 1] smbd/service.c:close_cnum(801) scgad2 (90.0.0.149) closed connection to service raid
L. Mark Stone
2004-Aug-04 17:11 UTC
[Samba] Transfer Problems when updated to version 3.0.5
On Wednesday 04 August 2004 12:20, Edward wrote:> I'm having some issues writing large files to my samba share. > After about 11Gb it fails ( for the past three transfer attempts). > The Files are sized between 2Gb and 65gb respectivelyWe just went through something similar at one client's site. What we found was that the Cisco switches there don't auto negotiate effectively with the NICs on the Samba (and other) server(s) and workstations. Once we forced all the NICs on the network to 100FD, our problems went away. In other words, this wasn't a Samba problem at all. On a Windows box, check the driver settings on the NIC to disable autoneg and force whatever your network infrastructure will comfortably support, usually 100FD. If you have heavy network traffic, you can set the workstations to 10FD and leave the servers at 100FD (or, leave the workstations at 100FD but add more NICs to the servers). On the Samba box, you'll need to use ethtool or mii-tool, depending on your NIC, to make the changes. The man pages for these tools are pretty clear as to their usage. Hope this helps, Mark -- ___________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 (207) 772-5678