Hello,
I hope anybody can help me with the following tough problem. We are
running a samba-server (3.0.7) for providing fileservices for our
constructions department. Since 2 Weeks we encounter problems with 2 of
our workstations, running under win xp professional (The third xp
workstation and the 2 running under win2k do not have this
problem). The cad program tell's me, that it can not set the write
lock correct. It seams to be a problem with oplocks because the only
thing I can find in the log is the following:
[2005/03/21 16:10:51, 2, effective(10001, 1000), real(10001, 0)]
smbd/close.c:close_normal_file(262)
konst07 closed file 3d_daten/System_4000/Anwendungen_41~a.SLDDRW (numopen=2)
[2005/03/21 16:10:51, 3, effective(10001, 1000), real(10001, 0)]
smbd/oplock.c:initial_break_processing(550)
initial_break_processing: called for dev = fe03, inode = 507499042 file_id =
433
Current oplocks_open (exclusive = 1, levelII = 1)
[2005/03/21 16:11:21, 0, effective(10001, 1000), real(10001, 0)]
smbd/oplock.c:oplock_break(839)
oplock_break: receive_smb timed out after 30 seconds.
<-----posible error>
oplock_break failed for file 3d_daten/System_4000/Anwendungen_41~a.SLDASM (dev
= fe03, inode = 507499042, file_id = 433).
[2005/03/21 16:11:21, 3, effective(10001, 1000), real(10001, 0)]
smbd/oplock.c:initial_break_processing(550)
initial_break_processing: called for dev = fe03, inode = 507499042 file_id =
433
Current oplocks_open (exclusive = 1, levelII = 1)
[2005/03/21 16:11:21, 0, effective(10001, 1000), real(10001, 0)]
smbd/oplock.c:oplock_break(911)
oplock_break: client failure in oplock break in file
3d_daten/System_4000/Anwendungen_41~a.SLDASM <-----posible error>
[2005/03/21 16:11:21, 3, effective(10001, 1000), real(10001, 0)]
smbd/oplock.c:oplock_break(935)
oplock_break: returning success for dev = fe03, inode = 507499042, file_id =
433
Current exclusive_oplocks_open = 0
[2005/03/21 16:11:21, 2, effective(10001, 1000), real(10001, 0)]
smbd/open.c:open_file(245)
konst07 opened file 3d_daten/System_4000/Anwendungen_41~a.SLDASM read=Yes
write=No (numopen=3)
[2005/03/21 16:12:03, 3, effective(10001, 1000), real(10001, 0)]
smbd/process.c:timeout_processing(1332)
timeout_processing: End of file from client (client has disconnected).
[2005/03/21 16:12:03, 3, effective(10001, 1000), real(10001, 0)]
smbd/sec_ctx.c:set_sec_ctx(288)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2005/03/21 16:12:03, 2, effective(0, 0), real(0, 0)]
smbd/server.c:exit_server(571)
Closing connections
This error does only appear at some files. Others work just fine. The
error occurs everytime the file is accessed. After a restart of samba
the problem went away for about an hour but came back after that. :-(
Thanks in advance for any help or info where to look for a solution.
Regardes
Achim Kern
IT-Manager
HIRSCHMANN GMBH
Kirchentannenstr. 9
D-78737 Fluorn-Winzeln
Tel.: (+49) 07402/183-24
Fax: (+49) 07423/183-9924
EMail: achimkern@hirschmanngmbh.com
WWW: www.hirschmanngmbh.com
The configuration data:
The clients run under win xp professional sp 1
Server:
Debian Linux with a custom kernel: 2.4.27
Samba: 3.0.7
smb.conf:
[global]
workgroup = konst_dom
server string = %h server (samba %v)
netbios name = srv05
os level = 84
local master = yes
domain master = yes
preferred master = true
domain logons = yes
wins support = yes
name resolve order = host lmhosts
dns proxy = yes
time server = yes
########### Authentication ############
passdb backend = ldapsam:ldap://localhost:389/
ldap admin dn = cn=admin,dc=hirschmann,dc=de
ldap suffix = dc=hirschmann,dc=de
ldap user suffix = ou=people
ldap group suffix = ou=groups
ldap machine suffix = ou=machines
idmap backend = ldap:ldap://localhost:389/
ldap idmap suffix = ou=idmap,dc=hirschmann,dc=de
idmap uid = 1000-200000
idmap gid = 1000-200000
template shell = /bin/bash
#obey pam restrictions = yes
#invalid users = root
security = user
encrypt passwords = true
unix password sync = no
pam password change = no
admin users = @root, administrator
guest account = nobody
map to guest = Bad User
dos filemode = yes
########### Logging ############
log level = 3
log file = /var/log/samba/log.%m
max log size = 40960
syslog only = no
syslog = 0
debug uid = yes
panic action = /usr/share/samba/panic-action %d
########### Logon ############
logon path = \\srv05\profiles\%U
logon home = \\srv05\%U\.profiles
logon drive = w:
logon script = %U.bat
########## Printing ##########
load printers = yes
printing = cups
printcap name = cups
printer admin = @root, administrator
######## File sharing ########
; preserve case = yes
; short preserve case = yes
locking = yes
kernel oplocks = yes
#use sendfile = no
unix charset = ISO8859-15
############ Misc ############
; include = /home/samba/etc/smb.conf.%m
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY
#======================= Share Definitions ======================
[homes]
comment = Home Directories
browseable = no
writable = yes
create mask = 0700
directory mask = 0700
.....
#The errors occur on this share
[konstruktion]
comment = Gruppenlaufwerk Konstruktion
path = /home/groups/konstruktion
browsable = no
writeable = yes
create mask = 0770
directory mask = 0770
[cnc]
comment = Gruppenlaufwerk NC/CNC Programmierung
path = /home/groups/cnc
browsable = no
writeable = yes
# Rechte f?r others m?ssen gesetzt sein, da sonst der
# dnc-Betrieb nicht funktioniert (dos nfs hat keinen Zugriff auf die
# nc Programme)
create mask = 0666
directory mask = 0777
[public]
comment = Public-Laufwerk
path = /home/public
browsable = yes
writeable = yes
guest ok = yes
# die n?chsten 3 Eintr?ge sind notwendig, damit die
# fmea-Anwendung von Herrn Unger l?uft. Wird diese auf ein anderes
# share verlegt, k?nnen die Entr?ge gestrichen werden.
create mask = 0666
force create mode = 0666
directory mask = 0777
veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/*.mbb/*.MBB/*.mdd/*.MDD/
[serverlinux]
comment = Altlast Serverlinux
path = /home/public/serverlinux
browsable = yes
writeable = yes
guest ok = yes
create mask = 0666
force create mode = 0666
directory mask = 0777