request_oplock_break message in log files
Giulio Orsero
giulioo at pobox.com
Tue Aug 22 14:38:31 GMT 2000
On Wed, 23 Aug 2000 00:22:50 +1000, you wrote:
>|¯-------
>|[2000/08/22 08:28:09, 0] smbd/oplock.c:request_oplock_break(1202)
>| request_oplock_break: no response received to oplock break request
>to pid
>| 20772 on port 54910 for dev = 19801c3, inode = 4582438
I had these in the past too.
In my case it was linux with win9x clients.
> This is a client disconnecting, hanging, crashing or
> just timing out.
Yes, but for samba only. The clients were alive and could do everything.
The clients had these problem accessing samba shares only.
My advice is:
oplocks = no
It's better to get a constant performance degradation than random
freezes.
--
giulioo at pobox.com
More information about the samba
mailing list