I am sorry for the misleading term "crashes" in the titel, but I didn't find any better expression while writing the bug report. samba does not crash/segfault, rather it raises the CPU load to 100%. Don't know how to call this.
Today I tested several file sizes and stopped at about 3500MB. It seems that there is no static border as a file with this size works in some case and it several others, it does not work and causes the above described problem. If a file is below this threshold, the probability is very high that the transmission will work. I also raised the log level in samba to see what happens within samba and found the following: [2009/11/12 21:00:24, 0] lib/util_sock.c:730(write_data) [2009/11/12 21:00:24, 0] lib/util_sock.c:1468(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer [2009/11/12 21:00:24, 0] smbd/process.c:62(srv_send_smb) Error writing 62 bytes to client. -1. (Transport endpoint is not connected) [2009/11/12 21:00:24, 0] lib/util_sock.c:730(write_data) [2009/11/12 21:00:24, 0] lib/util_sock.c:1468(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected write_data: write failure in writing to client 0.0.0.0. Error Broken pipe [2009/11/12 21:00:24, 0] smbd/process.c:62(srv_send_smb) Error writing 104 bytes to client. -1. (Transport endpoint is not connected) [2009/11/12 21:00:24, 0] lib/util_sock.c:1468(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2009/11/12 21:00:24, 0] lib/util_sock.c:730(write_data) [2009/11/12 21:00:24, 0] lib/util_sock.c:1468(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected write_data: write failure in writing to client 0.0.0.0. Error Broken pipe [2009/11/12 21:00:24, 0] smbd/process.c:62(srv_send_smb) Error writing 60 bytes to client. -1. (Transport endpoint is not connected) [2009/11/12 21:00:24, 0] lib/util_sock.c:730(write_data) [2009/11/12 21:00:24, 0] lib/util_sock.c:1468(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected write_data: write failure in writing to client 0.0.0.0. Error Broken pipe [2009/11/12 21:00:24, 0] smbd/process.c:62(srv_send_smb) Error writing 53 bytes to client. -1. (Transport endpoint is not connected) [2009/11/12 21:00:24, 2] smbd/close.c:612(close_normal_file) christoph closed file large.001 (numopen=0) NT_STATUS_OK -- Samba daemon crashes when transfering large files to share in encrypted home dir https://bugs.launchpad.net/bugs/480849 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
