ms word and samba 2.0.6 problems

Todd Pfaff pfaff at
Thu Jan 20 23:50:41 GMT 2000

On Fri, 21 Jan 2000, Giulio Orsero wrote:

> On Fri, 21 Jan 2000 03:06:43 +1100, hai scritto:
> >Lots of noise in the log files about "Unable to get oplock". 
> If it's "oplock_break failed for file ....." then you can solve it with
> oplocks = no.

yes, in my case, it appears that there are lots of oplock_break messages
logged when the problem occurs.  for example:

[2000/01/20 14:59:52, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[2000/01/20 15:00:02, 0] smbd/oplock.c:oplock_break(922)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file summary.doc (dev = b, inode = 215094).
[2000/01/20 15:00:02, 0] smbd/oplock.c:oplock_break(992)
  oplock_break: client failure in break - shutting down this smbd.

in case it has any bearing, this is on a linux samba server (redhat 6.0,
samba-2.0.6).  however, we see similar problems on both this server and
other samba-2.0.6 servers running solaris 7.

i'm going to try oplocks=no on one of our shares and i'll let you know if
this solves the problem.

however, if this works, is the only solution to this problem to disable
oplocks and suffer the performance loss as described in Speed.txt?

does this problem suggest a flaw in oplock handling in samba-2.0.6?
if so, has this possibly been fixed in more recent code?
if not, is this likely a problem with the nt client or ms word?

Todd Pfaff                         \  Email: pfaff at
Computing and Information Services  \ Voice: (905) 525-9140 x22920
ABB 132                              \  FAX: (905) 528-3773
McMaster University                   \
Hamilton, Ontario, Canada  L8S 4M1     \

More information about the samba mailing list