oplock problems with Version 2.2.2

[David Collier-Brown]

Thomas Schulz wrote:
> 
> I just tried to upgrade from Version 2.0.7 to Version 2.2.2 and ran into
> oplock errors.  I made no changes to the configuration file.  We are running
> Samba on a Sun Solaris 2.6 machine.  The PC is running Windows 2000.  The
> aplication showing the problem is ISP Design Expert from Lattice
> Semiconductor. The lines in the configuration file having to do with locks
> are:
> 
>    level2 oplocks = true
>    lock directory = /opt/local/samba/var/locks/%h
> 
> The entries in the log file are:
> 
> [2002/01/14 09:03:19, 0] smbd/oplock.c:(813)
>   oplock_break: no break received from client within 30 seconds.
>   oplock_break failed for file Projects/79152-RollsDerby/boardDesigns/Isource/PL
> D/automake.log (dev = 800006, inode = 4281608).

	Hmmn, sounds like the client (meaning
	the PC SMB program) that had the file
	open when the new user wanted to open
	it didn't respond to an oplock break, 
	but was running, as there wasn't a 'lost 
	connection' message.

> [2002/01/14 09:03:19, 0] smbd/oplock.c:(859)
>   oplock_break: client failure in oplock break in file Projects/79152-RollsDerby
> /boardDesigns/Isource/PLD/automake.log


> [2002/01/14 09:03:19, 0] smbd/reply.c:(4413)
>   reply_lockingX: Error : oplock break from client for fnum = 9046 and no oplock
>  granted on this file (Projects/79152-RollsDerby/boardDesigns/Isource/PLD/automa
> ke.log).

	Ok, the lock is denied.
> 
> The user reported that a save operation that usually takes less than
> one second took over a minute to complete.  I have reverted to Version 2.0.7
> and the problem is gone.

	Should I assume this was
	- occasional
	- repeated erratically
	- every time?

--adve
-- 
David Collier-Brown,           | Always do right. This will gratify 
Performance & Engineering      | some people and astonish the rest.
Americas Customer Engineering, |                      -- Mark Twain
(905) 415-2849                 | davecb at canada.sun.com