[Samba] Oplock Break

Joel Hammer Joel at HammersHome.com
Fri Jun 21 14:07:02 GMT 2002

Oplocks are really a bad idea, they say. With oplocks, Windows caches
the data locally to speed things up, but,if the network is bad and slow,
oplocks don't work either, because other clients can't access the data
because another client has that data cached locally. If the oplock
connection to the server is lost because of a bad network connection,
then data corruption is possible. (This is what I have heard said or
implied on this list.)

Try turning oplocks off.


On Fri, Jun 21, 2002 at 04:18:25PM -0400, Scott Sipe wrote:
> I got this error message today (have never seen it with 2.2.4)
> [2002/06/21 14:30:38, 0] smbd/oplock.c:oplock_break(796)
>   oplock_break: receive_smb timed out after 30 seconds.
>   oplock_break failed for file user/prices 7.02.qpw (dev = 29d03, inode =
>   2998188, file_id = 2228).
> [2002/06/21 14:30:38, 0] smbd/oplock.c:oplock_break(868)
>   oplock_break: client failure in oplock break in file user/prices 7.02.qpw
> [2002/06/21 14:30:38, 0] smbd/reply.c:reply_lockingX(4490)
>   reply_lockingX: Error : oplock break from client for fnum = 10509 and no
>   oplock granted on this file (user/prices 7.02.qpw).
> Now, I see that it says "client failure," however I checked the logs on
> the client computer, and see no evidence of a crash (XP computer). 
> However, I think Quatro Pro (.qpw) is fairly unstable, so it's possible it
> was a program crash that for some reason didn't show up in the logs.
> Should I be worried about this error?
> thanks,
> Scott
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

More information about the samba mailing list