[Samba] writing files via samba issues...
jra at samba.org
Mon Oct 24 19:30:18 GMT 2005
On Mon, Oct 24, 2005 at 02:18:23PM -0500, Satyajit Ketkar wrote:
> I've samba running an embedded linux system (2.6.x kernel with uClibc). I'm trying to transfer some medium to large files (65-225 MB). I'm using simple windows explorer drag/drop to write the files to the embedded system. The file transfer dialog will show some progress then lock up for a few minutes. After this it reports with "The specified network name is no longer availabe." Then after a few seconds the file will show up on the embedded system but will be totally useless (I did a compare on it with the original).
> Here is what the "log.winxptest" file tailed shows,
> smbd/service.c:make_connection(550) winxptest (192.168.1.102) connect to service data as user winxpuser (uid=501, gid=500) (pid 241)
> lib/util_sock.c:client_addr(1061) getpeername failed. Error was Transport endpoint is not connected
> lib/util_sock.c:write_socket_data(540) write_socket_data: write failure. Error = Connection reset by peer
> lib/util_sock.c:write_socket(566) write_socket: Error writing 4 bytes to socket 3: ERRNO = Connection reset by peer
> lib/util_sock.c:send_smb(754) Error writing 4 bytes to client. -1. Exiting
> I can't delete the file through samba now after this either. Reading files from the embedded system have no problems.
Might be a bug on the embedded Linux. You need to look at an
ethereal trace to see why the network connection is being
More information about the samba