I've been using Samba for a number of years and suddenly Samba started
throwing oplock errors and I simply can't figure out why. I've not
changed
any config parameters in some time, but have updated my version of samba as
new packages become available for my distro.
I'm running Centos 5.9 and the following versions of samba from stock
Centos:
samba3x-common-3.6.6-0.129.el5
samba3x-winbind-3.6.6-0.129.el5
samba3x-client-3.6.6-0.129.el5
samba3x-3.6.6-0.129.el5
Suddenly, over the last 2 weeks or so, I started to get the following types
of oplock errors:
Mar 11 08:57:38 fileserver smbd[22536]: [2013/03/11 08:57:38.925861, 0]
smbd/oplock_linux.c:104(linux_oplock_signal_handler)
Mar 11 08:57:38 fileserver smbd[22536]: linux_oplock_signal_handler:
failed to find fsp for file fd=51 (file was closed ?)
Mar 11 08:57:49 fileserver smbd[22536]: [2013/03/11 08:57:49.685736, 0]
smbd/oplock_linux.c:158(linux_release_kernel_oplock)
Mar 11 08:57:49 fileserver smbd[22536]: linux_release_kernel_oplock:
Error when removing kernel oplock on file Bids and
Proposals/2011/11-Nov/someproject/sol/Project White Paper - 2.1.docx,
file_id = fd05:70045:0, gen_id = 3041820832. Error was Bad file descriptor
My samba machine is setup as as a domain member of a legacy (win nt 4) type
domain against a another Samba server that is running authentication.
I have the following oplock options set is my smb.conf file:
oplocks = true
kernel oplocks = true
level2 oplocks = true
and the share is setup with the following config:
[management]
comment = Management Drive
path = /home/files/dir/management/files
read only = no
writable = yes
force group = shared
printable = no
inherit permissions = yes
create mode = 0660
Any suggestions would be much appreciated.
Greg
