SAMBA 2.0.5a oplock_break: client failure in break

Ole Holm Nielsen Ole.H.Nielsen at
Wed Sep 8 13:27:12 GMT 1999

We are running Samba 2.0.5a on an AIX 4.2.1 box, and since
we upgraded from 1.9.18, a Windows 95 client reports
intermittent problems (timeouts) when saving small files.
The log.smb file has entries from those events:

[1999/09/08 14:59:07, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[1999/09/08 14:59:17, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[1999/09/08 14:59:27, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[1999/09/08 14:59:37, 0] smbd/oplock.c:oplock_break(922)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file breve/weco.tex (dev = 290001, inode = 621734).
[1999/09/08 14:59:37, 0] smbd/oplock.c:oplock_break(992)
  oplock_break: client failure in break - shutting down this smbd. 

After reading the manual I though that this line in smb.conf
ought to solve the problem:
   oplock break wait time = 50
However, this does not improve things (I even tried 250 msecs).

So something is going wrong with the oplocks, and even if
one may blame Windows 95, my question is:  What should I
do to eliminate this oplock problem ?  Is it really a 
client problem ?

Ole H. Nielsen
Department of Physics, Technical University of Denmark,

More information about the samba mailing list