Locking problems in 2.2.2

[Jeremy Allison]

On Mon, Dec 03, 2001 at 03:48:47PM +0100, Jurjen Oskam wrote:
> 
> [2001/12/03 11:37:48, 0] smbd/oplock.c:oplock_break(786)
>   oplock_break: receive_smb timed out after 30 seconds.
>   oplock_break failed for file
> Homepage/commercieel/Mailing/Antwoordkaart/20011106, Antwoordkaart
> Voorkant.doc (dev = 90b, inode = 995866).
> [2001/12/03 11:37:48, 0] smbd/oplock.c:oplock_break(859)
>   oplock_break: client failure in oplock break in file
> Homepage/commercieel/Mailing/Antwoordkaart/20011106, Antwoordkaart
> Voorkant.doc
>   reply_lockingX: Error : oplock break from client for fnum = 5741 and no
> oplock granted on this file
> (Homepage/commercieel/Mailing/Antwoordkaart/20011106, Antwoordkaart
> Voorkant.doc).
> 
> and:
> 
> [2001/12/03 08:04:27, 0] smbd/oplock.c:oplock_break(786)
>   oplock_break: receive_smb timed out after 30 seconds.
>   oplock_break failed for file notulen/ava/AVAuitstel2000.doc (dev = 90b,
> inode = 1012151).
> [2001/12/03 08:04:27, 0] smbd/oplock.c:oplock_break(859)
>   oplock_break: client failure in oplock break in file
> notulen/ava/AVAuitstel2000.doc
>   reply_lockingX: Error : oplock break from client for fnum = 9039 and no
> oplock granted on this file (notulen/ava/AVAuitstel2000.doc).
> 
> 
> These errors occur both with and without oplock break wait time = 15 in
> smb.conf.
> 
> Is it useful to try the SAMBA_2_2 CVS tree with these conditions?

Looks like your clients are failing to respond to oplock
breaks. New Samba code won't fix that, I'd check the NIC
cards/hubs/network between the server and clients. This
is commonly the problem if this kind of thing happens
often.

It would still help Samba if you could try the 2.2 CVS
tree though, to see if everything else works ok, although
the particular problems you've listed here aren't problems
Samba can do much about.

Jeremy.