oplock_break: client failure in break - shutting down

[Bruce Tenison]

We recently tried the upgrade to 2.0 Beta series (just finished testing
Beta 4) on our network.  Everything works fine with 1.9.18pl10, but once
we start 2.0 in its place we start getting the following in the log files:

[1998/12/17 05:00:12, 1] smbd/files.c:file_init(219)
  file_init: Information only: requested 10000 open files, 246 are
available.
[1998/12/17 05:07:52, 1] smbd/service.c:make_connection(484)
  vhawsey (192.168.1.2) connect to service virus as user vhawsey (uid=503,
gid=100) (pid
 16637)
[1998/12/17 05:09:27, 1] smbd/service.c:make_connection(484)
  ost15 (192.168.2.142) connect to service tmobley as user tmobley
(uid=742, gid=100) (p
id 17398)
[1998/12/17 06:10:53, 1] smbd/service.c:make_connection(484)
  ost15 (192.168.2.142) connect to service virus as user tmobley (uid=742,
gid=100) (pid
 17398)
[1998/12/17 06:32:48, 1] smbd/service.c:make_connection(484)
  long (192.168.2.5) connect to service virus as user elong (uid=530,
gid=100) (pid 2492
0)
[1998/12/17 06:33:20, 0] smbd/oplock.c:request_oplock_break(942)
  request_oplock_break: no response received to oplock break request to
pid 17398 on por
t 1502 for dev = 301, inode = 620605
[1998/12/17 06:33:28, 0] smbd/oplock.c:oplock_break(734)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file COMM.INF (dev = 301, inode = 620605).
[1998/12/17 06:33:28, 0] smbd/oplock.c:oplock_break(804)
  oplock_break: client failure in break - shutting down this smbd.
[1998/12/17 06:33:28, 1] smbd/service.c:close_cnum(510)
  ost15 (0.0.0.0) closed connection to service virus
[1998/12/17 06:33:28, 1] smbd/service.c:close_cnum(510)
  ost15 (0.0.0.0) closed connection to service tmobley
[1998/12/17 06:33:34, 1] smbd/service.c:make_connection(484)
  long (192.168.2.5) connect to service virus as user elong (uid=530,
gid=100) (pid 2530
1)
[1998/12/17 06:33:52, 0] smbd/oplock.c:request_oplock_break(942)
  request_oplock_break: no response received to oplock break request to
pid 17398 on por
t 1502 for dev = 301, inode = 620605
[1998/12/17 06:33:52, 1] smbd/service.c:close_cnum(510)
  long (0.0.0.0) closed connection to service virus
[1998/12/17 07:03:45, 1] smbd/service.c:make_connection(484)
  jordan (192.168.1.3) connect to service virus as user mcjordan (uid=832,
gid=100) (pid
 7254)
[1998/12/17 07:07:28, 1] smbd/service.c:make_connection(484)
  mcbride (192.168.1.12) connect to service virus as user umcbride
(uid=532, gid=100) (p
id 9067)
[1998/12/17 07:08:43, 1] smbd/service.c:make_connection(484)
  ssmith (192.168.1.9) connect to service virus as user ssmith (uid=872,
gid=100) (pid 9
676)
[1998/12/17 07:08:58, 0] lib/doscalls.c:dos_GetWd(405)
  Very strange, couldn't stat "."


What really bothers me is the section concerning the oplock_break
problems.  It seems that everything churns along fine with no noticable
speed decrease until these messages start cropping up in the log files.
We have roaving profiles and desktops, and once these messages start
appearing in the log files, things screech to a halt, and most (if not
all) of the computers will "halt".  As you can see the share that is
causing the problem here is the virus share (F-SECURE anti-virus
communication directory)

I can reproduce this pretty much at will (just have to reinstall 2.0).
Are there any ideas about how to fix this (is it a bug, or is it my
configuration???)  It seems strange to me that 1.9.18pl10 works fine and
2.0 doesn't with the same smb.conf (minus the minor unrelated changes that
we made for 2.0)

Any ideas?

Thanks!

Bruce Tenison
btenison at dibbs.net

All the world's a stage, and we are merely players