Ralf Hildebrandt
2003-Jul-31 14:24 UTC
[Samba] oplock_break: client failure in oplock break in file ...
Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success) oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_Enaikoon2_AZK.doc (dev = 301, inode = 2469225, file_id = 18). [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 16:07:22, 1] smbd/service.c:make_connection_snum(692) gustavo (10.0.0.20) connect to service public initially as user braun (uid=1000, gid=100) (pid 3511) [2003/07/31 16:07:53, 0] smbd/oplock.c:oplock_break(795) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 1). [2003/07/31 16:07:53, 0] smbd/oplock.c:oplock_break(867) oplock_break: client failure in oplock break in file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc With both samba-3.0.0beta2-1 (Debian/unstable) and 2.2.3a (Debian/testing) Kernel 2.4.20-3-686 This is an environment with a Windows XP box and a Windows 98 box, which both access the server. The directories accessed are on a ext3 filesystem. smb.conf is attached. What is the reason? Are there workarounds for this? -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite Campus Mitte Tel. +49 (0)30-450 570-155 Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 AIM: ralfpostfix -------------- next part -------------- [global] panic action = /usr/share/samba/panic-action %d workgroup = GWFOEHLER server string = %h server (Samba %v) load printers = yes printcap name = cups printing = cups guest account = nobody invalid users = root log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 security = user encrypt passwords = true passdb backend = smbpasswd guest domain logons = yes socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY local master = yes os level = 64 domain master = yes preferred master = yes wins support = yes dns proxy = no preserve case = yes short preserve case = yes unix charset = ISO8859-1 passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . deadtime = 1 obey pam restrictions = yes logon home = \\%L\%U\.profile logon drive = H: logon path = \\%L\profiles\%U logon script = netlogon.bat [homes] comment = Home Directories browseable = no writable = yes create mask = 0640 directory mask = 0750 [netlogon] comment = Network Logon Service path = /home/samba/netlogon guest ok = yes writable = no share modes = no [profiles] path = /home/samba/profiles writeable = yes browseable = no create mask = 0600 directory mask = 0700 [printers] comment = All Printers path = /tmp public = yes guest ok = yes browseable = no writable = no printable = yes create mode = 0700 [public] comment = Public Area path = /data/public public = yes writable = yes create mask = 774 directory mask = 775 browseable = yes [cdrom] comment = Samba server's CD-ROM writable = no locking = no path = /var/autofs/misc/cd public = yes
Ralf Hildebrandt
2003-Jul-31 20:15 UTC
[Samba] oplock_break: client failure in oplock break in file ...
* Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>:> oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). > [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) > oplock_break: client failure in break - shutting down this smbd. > [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) > oplock_break: receive_smb error (Success) > oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_Enaikoon2_AZK.doc (dev = 301, inode = 2469225, file_id = 18). > [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(843) > oplock_break: client failure in break - shutting down this smbd. > [2003/07/31 16:07:22, 1] smbd/service.c:make_connection_snum(692) > gustavo (10.0.0.20) connect to service public initially as user braun (uid=1000, gid=100) (pid 3511) > [2003/07/31 16:07:53, 0] smbd/oplock.c:oplock_break(795) > oplock_break: receive_smb timed out after 30 seconds. > oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 1). > [2003/07/31 16:07:53, 0] smbd/oplock.c:oplock_break(867) > oplock_break: client failure in oplock break in file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc > > With both samba-3.0.0beta2-1 (Debian/unstable) and 2.2.3a (Debian/testing) > Kernel 2.4.20-3-686 > > This is an environment with a Windows XP box and a Windows 98 box, which both access the server. > > The directories accessed are on a ext3 filesystem. > > smb.conf is attached. What is the reason? Are there workarounds for > this?Like turning off oplocks? (Whatever that may be) -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite Campus Mitte Tel. +49 (0)30-450 570-155 Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 AIM: ralfpostfix