oplock_break problem

[Eric Sisler]

>>I have referred to the archive and some of you were having the oplock_break 
>>problem. Does anyone have any solution for this? Will reboot fix the
problem?

>>From the samba faq:
>===
>The advisory message means that you have either a defective network card
>on one of your clients, or else an MS Windows application is refusing to
>respond to an oplock break request from another MS Windows client that
>wishes to accessan already locked file.
>===
>So check your nic's and cabling.

There has to be another answer to this problem.  I went from
samba-1.9.18p10-52.4 on RedHat 5.2 to the 2.0.x release and back to 1.9.18
because of this problem.  The *only* thing that changed was the version of
Samba.  The clients, network cards, cabling, etc., all stayed exactly the
same.

It's probably not very scientific, but a quick count of the number of times
"oplock" occured in the samba logfiles revealed the following for ~120
clients:

samba 2.0.3, running for 1 week = 549 times
samba 1.9.18 running for 2 weeks = 37 times

Ouch!  The only other thing I can think of is a missing service pack or
update to Windows.  (We're using Win '95 clients.)  Does anyone know if
there's an update that addresses this problem?

-Eric


Eric Sisler
Library Computer Technician
Westminster Public Library
Westminster, CO, USA
esisler at westminster.lib.co.us

Linux - don't fear the Penguin.
Want to know what we use Linux for?
Visit http://gromit.westminster.lib.co.us/linux