Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS

Richard Bollinger rabollinger at
Fri May 24 19:30:02 GMT 2002

Right... or if it times out because of the dead time setting... so it's shouldn't be that rare
in the wild.  I have a feeling that a lot of folks just disable oplocks to avoid the "troubles".
My test at work showed that the problem did not occur with a W2K server when I forced the
disconnect from the server end.

Rich B

----- Original Message -----
From: "Jeremy Allison" <jra at>
To: "Richard Bollinger" <rabollinger at>
Cc: "Jeremy Allison" <jra at>; "Samba Technical" <samba-technical at>
Sent: Friday, May 24, 2002 10:21 PM
Subject: Re: Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS

On Fri, May 24, 2002 at 02:05:12PM -0400, Richard Bollinger wrote:
> OK... time for a brain flush and refill...
> I went back and verified my test conditions and determined that the same failure can be
> with every server platform we own running Samba 2.X with oplocks enabled and with a Win98
> Here's the setup:
> On Win98 client:
>     net use i: \\server\share1
> On Server:
>     smbd instance goes away by dead time exceeded or with kill command
> On Win98 client:
>     net use j: \\server\share2
>     j:
>     cd netbench
>     netbench.exe                <<<--- here's where we get the oplock freeze for 30 seconds
> I can send you a copy of the netbench directory off list if you need it.  I suspect the same
> will happen for any DOS executable.

Ok - I've been looking at this - it only happens if the smbd has
been killed in between the first and second net use commands.

The client repeatably fails to respond to a valid oplock break request....

I'm looking into this more.


More information about the samba-technical mailing list