[Samba] smbd/oplock.c:oplock_timeout_handler(375) after samba upgrade

mrosamba at eastgranby.k12.ct.us mrosamba at eastgranby.k12.ct.us
Mon Apr 24 21:14:14 GMT 2006

I recently upgraded from samba 3.0.10-1.fc3 to 3.0.21b-2 running on FC5. 
Today was the first day of a typing class which uses the network version
of Mavis Beacon Typing which depends on file sharing.

The users are hanging and then getting an error message during logging
into the product.  In /var/log/message, I can see the following message
for each user similar to:

[2006/04/24 09:45:24.177906, 0] smbd/oplock.c:oplock_timeout_handler(375)
  Oplock break failed for file mavis/Mavis15EEVNet/Mav15UserData/Ali
Johnson.rec -- replying anyway

Each user has a different filename for the above message.

Below is the smb.conf share.  Note the force user.

    comment = Mavis Beacon Typing
    available = yes
    path = "/home/mavistype"
    public = no
    guest only = no
    writable = yes
    browseable = yes
    only user = no
    force user = mavistype

As a workaround, I have added the following to the share and will know
tomorrow (Tuesday) whether it worked.

    csc policy = disable
    oplocks = no
    level2 oplocks = no

I don't know why this oplock break is occuring because to the best of my
knowledge, each user is using a separate file.

I really need some help here.

In searching the log, I also noticed the following has occured multiple
times since the upgrade /var/log/messages and in several
/var/log/samba/log. files.

Apr 24 07:28:40 hssrv01 smbd[11138]: [2006/04/24 07:28:40.384041, 0]
Apr 24 07:28:40 hssrv01 smbd[11138]:   Oplock break failed for file
logon.bat -- replying anyway

The netlogon share is below.  Note that it omits share modes = no

    path = /home/netlogon
    writeable = no
    guest only = no

Could either of these possibly be related to the "reset on zero vc"
parameter?  When did this parameter go into samba?

Mark Orenstein
East Granby (CT, USA) School System

More information about the samba mailing list