Oplock Problems

Kim Malafant kim at complexia.com.au
Thu Mar 29 22:12:31 GMT 2001


Dear All,

I know that the following error for "oplocks" appears in the FAQ but we
need an "authorative" answer to the problem so that we can advise a client
what to do. Having a large number of cables/cards etc tested is expensive.
The logfile output is:

[2001/03/23 11:04:21, 1, pid=16808, effective(0, 300), real(0, 0)]
smbd/service.c:(550)
  roger (172.16.12.18) connect to service testarea as user kim (uid=0,
gid=300) (pid 16808)
[2001/03/23 11:04:34, 0, pid=16808, effective(0, 0), real(0, 0)]
smbd/service.c:(336)
  kim logged in as admin user (root privileges)
[2001/03/23 11:04:34, 1, pid=16808, effective(0, 300), real(0, 0)]
smbd/service.c:(550)
  roger (172.16.12.18) connect to service test4kim as user kim (uid=0,
gid=300) (pid 16808)
[2001/03/23 11:05:42, 0, pid=16808, effective(0, 300), real(0, 0)]
smbd/oplock.c:(1204)
  request_oplock_break: no response received to oplock break request to pid
16749 on port 33722 for dev = 2680062, inode = 486401
  for dev = 2680062, inode = 486401, tv_sec = 3aba92cc, tv_usec = 22e4a
[2001/03/23 11:06:14, 0, pid=16808, effective(0, 300), real(0, 0)]
smbd/oplock.c:(1204)
  request_oplock_break: no response received to oplock break request to pid
16749 on port 33722 for dev = 2680062, inode = 486401
  for dev = 2680062, inode = 486401, tv_sec = 3aba92cc, tv_usec = 22e4a
[2001/03/23 11:06:43, 0, pid=16825, effective(0, 0), real(0, 0)]
smbd/service.c:(336)


which indicates that there is a bad network cable/card or an MS application
that does not understand oplocks correctly. So the questions are:

1) Will a bad network cable - this is a 100Mb network and the client makes
their own cables and has no test equipment - cause the problem? Can we
identify the machine/connection from the log file?

2) A faulty network card will also cause the same problem we believe. Is
this correct and if so how do we isolate that from the logfile?

These are the two "simple" fixes but if it is an MS application is there
any way of identifying that from the logfile? 

A clear and somewhat definitive answer would help greatly in convincing the
client that the problem is infrastructure related and not due to SAMBA.

Thanks in advance.


Kim Malafant
Director, compleXia
PO Box 3011, Belconnen
ACT, Australia, 2617
Phone: (02) 6253 8342
Fax:   (02) 6253 8346
Mobile: 0410 421 694




More information about the samba-technical mailing list