[Samba] Samba and oplock_break errors

[James Nord]

Kestutis Saldziunas wrote:

>Hello,
>
>I have recently migrated from Novell Netware file server to Samba 2.2.0-15.
>
Samba 2.2.0 had bad oplock problems, that were fixed in 2.2.1 & 2.2.2.
Some more were fixed in 2.2.3 (may be released tommorow).

I suggest upgrading to the latest 2.2.2 or if you can wait a day or two 
2.2.3 and see if you still have these problems.

/James

>
>For couple days I wondered how could new my Samba server work so well !
>However on next week users started complaining
>that their computers hang for minutes and displays errors (not found *.dll
>or fatal app error) when trying to start applications. Only Samba server
>restarting solved problems. It is related with oplocks so
>
>
>
>
>
>
>The black day log is such:
>
>In the day beginning:
>
>continiuos erros:
>
>[2002/01/21 10:00:32, 0] smbd/oplock.c:oplock_break(761)
>  oplock_break: end of file from client
>  oplock_break failed for file FORPOST/ICONS/SCRDWN2.ICO (dev = 900, inode =
>229061).
>[2002/01/21 10:00:32, 0] smbd/oplock.c:oplock_break(852)
>  oplock_break: client failure in break - shutting down this smbd.
>
>also some others rare errors:
>
>
>[2002/01/21 10:00:32, 0] smbd/oplock.c:oplock_break(852)
>  oplock_break: client failure in break - shutting down this smbd.
>
>
>[2002/01/21 10:57:46, 0] smbd/oplock.c:oplock_break(768)
>  oplock_break: receive_smb timed out after 30 seconds.
>  oplock_break failed for file FORPOST/ICONS/INFO.ICO (dev = 900, inode =
>229260).
>
>
>[2002/01/21 10:57:46, 0] smbd/oplock.c:oplock_break(841)
>  oplock_break: client failure in oplock break in file
>FORPOST/ICONS/INFO.ICO
>
>
>
>[2002/01/21 10:58:24, 0] lib/util_sock.c:read_socket_data(479)
>  read_socket_data: recv failure for 4. Error = Connection reset by peer
>
>
>[2002/01/21 11:06:02, 0] smbd/oplock.c:process_local_message(357)
>  process_local_message: Received unsolicited break reply - dumping info.
>[2002/01/21 11:06:02, 0] smbd/oplock.c:process_local_message(372)
>  process_local_message: unsolicited oplock break reply from pid 15199, port
>1275, dev = 900, inode = 1357219
>
>and at the day end continious errors:
>
>[2002/01/21 15:26:11, 0] smbd/oplock.c:request_oplock_break(995)
>  request_oplock_break: no response received to oplock break request to pid
>15966 on port 1649 for dev = 900, inode = 1880493
>  for dev = 900, inode = 1880493, tv_sec = 3c4c1457, tv_usec = 840a3
>
>After I restarted server and till now I have to restart server periodically
>each several days.
>
>
>
>
>
>
>
>
>


-- 
Technology is a word that describes something that doesn't work yet.
	Douglas Adams