What's an oplock_break?

Andrej Borsenkow borsenkow.msk at sni.de
Wed Oct 7 16:38:59 GMT 1998



> -----Original Message-----
> From: Rob Naccarato [mailto:rob.naccarato at sheridanc.on.ca]
> Sent: Wednesday, October 07, 1998 8:27 PM
> To: Andrej Borsenkow
> Cc: Multiple recipients of list
> Subject: RE: What's an oplock_break?
>
>
> On Wed, 7 Oct 1998, Andrej Borsenkow wrote:
>
>
> > > I've been seeing these in my logs files ever since I upgraded
> to 1.9.18p10
> > > and turned on oplock support for users' home directories:
> > >
> > > --snip --
> > > 1998/10/07 10:05:44 oplock_break: receive_smb timed out after
> 30 seconds.
> > > 1998/10/07 10:05:44 oplock_break failed for file Start
> Menu/Open Office
> > > Document.lnk (fnum = 14, dev = 808446, inode = 45cb8).
> > > 1998/10/07 10:05:44 oplock_break: client failure in break -
> shutting down
> > > this smbd.
> > > --snip --
> > >
> >
> > Are you sure you are running 1.9.18p10? Notably, this was the problem,
> > triggered by WinNT 4.0 Workstation bug. Workaround was
> available somewhen
> > about 1.9.18p4.
> >
>
> I am 100% positive that the server is running 1.9.18p10.  I don't have any
> WinNT clients.  All my clients are Win95.  Could this be an Explorer.exe
> problem instead?
>

'course, why not :))

You better send bug report to samba-bugs at samba.anu.edu.au The problem with
WinNT was hit by me at early alpha of 1.9.18; if I remember correctly, all
reports referred to NT as well. You seem to be the first one reporting it
for Win95.

For the time being, turn off oplocks if not absolutely needed.

/Andrej



More information about the samba mailing list