samba - Mar 1999 - Oplock break (again) End of file from client (PR#15037)

btenison@dibbs.net wrote:
> 
> I keep getting the following in the log files now that we've upgraded
to
> the latest cvs 2.0 branch.   Any ideas what we can do to fix this?
>
> Mar 23 08:45:34 gate smbd[22692]: [1999/03/23 08:45:34, 0]
> smbd/oplock.c:oplock_break(773)
> Mar 23 08:45:34 gate smbd[22692]:   oplock_break: end of file from client
> Mar 23 08:45:34 gate smbd[22692]:   oplock_break failed for file COMM.INF
> (dev = 301, inode = 620605).
> 
Brian,

	I'm forwarding this to the main Samba mailing list
as I think the reply will be of general interest. 

Herb & I (here at our lab at SGI) have finally managed
to reproduce this with 60 clients hitting the server in
a pathalogical test case and comparing the way Samba
responds with the way NT responds (I'm guessing this
is with Win95 clients, right ?).

The result is that we have a decent fix for this which
is in the 2.0 branch and will be available in 2.0.4 
(due soon-ish). 2.0.4 should make oplocks *much* more
reliable with Win95 clients (as we now do the same sneaky
thing that NT does to make them work all the time, rather
than just most of the time :-).

Regards,

	Jeremy Allison,
	Samba Team.


-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------