[Samba] corrupt files... oplocks?

JJB onephatcat at earthlink.net
Mon Apr 14 18:51:01 GMT 2008


Suddenly in the past week we have been having users who share excel 
files via our Samba complain that the file has become corrupt, and also 
some database files (Orcad .tdb database files). Fortunately there has 
in each instance been a good copy in the .recycler... so far.

I came across some docs and threads in the net about oplocks. I did find 
an error in the samba log:

[2008/04/14 10:19:05, 0] smbd/oplock.c:oplock_timeout_handler(351)

and there are some other errors that have been in the logs for a long 
time that we've been ignoring (because we were ignorant & nobody 
complained of any problems)

Apr 13 07:14:04 aa-samba smbd[10083]: [2008/04/13 07:14:04, 0] 
lib/util_sock.c:get_peer_addr(1229)
Apr 13 07:14:04 aa-samba smbd[10083]:   getpeername failed. Error was 
Transport endpoint is not connected
Apr 13 07:14:04 aa-samba smbd[10083]: [2008/04/13 07:14:04, 0] 
lib/util_sock.c:write_data(562)
Apr 13 07:14:04 aa-samba smbd[10083]:   write_data: write failure in 
writing to client 192.168.1.46. Error Connection reset by peer
Apr 13 07:14:04 aa-samba smbd[10083]: [2008/04/13 07:14:04, 0] 
lib/util_sock.c:send_smb(769)
Apr 13 07:14:04 aa-samba smbd[10083]:   Error writing 4 bytes to client. 
-1. (Connection reset by peer)

Should we add a line disabling oplocks in smb.conf, and if so, what 
would be the recommended approach?

 - Joel


More information about the samba mailing list