oplock problems with Version 2.2.2

[Jurjen Oskam]

On Mon, Jan 14, 2002 at 11:33:16AM -0500, Thomas Schulz wrote:

> [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).
> [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).
> 
> 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.

I also have these problems sporadically. The Samba-people say this is not a
fault in Samba, but most probably a faulty network cable or something
network related. I don't agree (but can't disprove it :-) ), because
I've seen more reports like yours (that the troubles disappear with another
version) and ifconfig reports *zero* errors on my Samba server:

RX packets:26297693 errors:0 dropped:0 overruns:0 frame:0
TX packets:20285562 errors:0 dropped:0 overruns:0 carrier:0



-- 
      Jurjen Oskam * http://www.stupendous.org/ for PGP key * Q265230
    6:43pm  up 11 days, 23:48,  1 user,  load average: 0.00, 0.00, 0.00