samba - Oct 2001 - no response received to oplock break request

Hi All,


My problem started with new server hardware and software update, also I
changed my network from 10 to 100Mb (New Cable and switches)
I have a problem with oplocks. I run Samba 2.0.10 (also tried 2.2.1a) on
Suse 7.1 Kernel 2.4. Several times a day I have an oplock error like this:
(request_oplock_break: no response received to oplock break request to pid
5312 on port 32857 for dev = 803, inode = 246701)
Sometimes it is possible for me to locate a client that hangs an give no
answer to the oplock request, and ok, WIN98ME Clients will hang sometimes,
but on one share I run a dos database Software (Cobol), and when there is an
oplock problem all clients hang and most time I have to restart samba.
Is there any one who knows what I can do?

What I tried is:
Setting
oplock contention limit = 5
oplock break wait time = 100

My settings are:
 # Samba config file created using SWAT
# Date: 2001/10/10 18:34:03

# Global parameters
[global]
	workgroup = SAMBA
	netbios name = FILESERVER
	server string = Samba %v
	encrypt passwords = Yes
	min password length = 2
	log file = /usr/local/samba/var/log.smbd
	nt acl support = No
	time server = Yes
	change notify timeout = 300
	shared mem size = 2097152
	socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=8192
	mangled stack = 100
	logon script = scripts\%U.bat
	domain logons = Yes
	os level = 65
create mask = 0777			only for test!!!
	force create mode = 0777
	directory mask = 0777
	force directory mode = 0777
	lm announce = False
	domain master = Yes
	dns proxy = No
	wins support = Yes
	kernel oplocks = No
	oplock break wait time = 100
	unix realname = Yes
	admin users = pemoeller reichwald
	write cache size = 64
	level2 oplocks = Yes
	oplock contention limit = 5

[homes]
	comment = Home-Verzeichnisse
	path = /home/%S
	writeable = Yes
	guest ok = Yes
	browseable = No
	delete readonly = Yes

[INKS]
	comment = Warenwirtschaft
	path = /home/public/inks
	force user = inks
	force group = users
	oplock contention limit = 5
	writeable = Yes
	guest ok = Yes
	browseable = No
	delete readonly = Yes

[netlogon]
	comment = logon-Scipte
	path = /home/public/system/netlogon
	valid users = @users
	admin users = pemoeller
	write list = @users
	writeable = Yes
	guest ok = Yes

[admin]
	comment = Fileserver
	path = /home
	guest account = pemoeller
	writeable = Yes
	browseable = No

[pool]
	comment = bon-Pool
	path = /home/public/pool
	writeable = Yes
	browseable = No
	delete readonly = Yes

[Handbuch]
	comment = ISO 9000 Handbuch
	path = /home/public/handbuch
	writeable = Yes
	browseable = No
	delete readonly = Yes


Thank you very much....


Enno Pem?ller
mailto:pemoeller@bonoptic.de
http://www.bonoptic.de/

Enno Pem?ller wrote:
> 
> Hi All,
> 
> My problem started with new server hardware and software update, also I
> changed my network from 10 to 100Mb (New Cable and switches)
> I have a problem with oplocks. I run Samba 2.0.10 (also tried 2.2.1a) on
> Suse 7.1 Kernel 2.4. Several times a day I have an oplock error like this:
> (request_oplock_break: no response received to oplock break request to pid
> 5312 on port 32857 for dev = 803, inode = 246701)
> Sometimes it is possible for me to locate a client that hangs an give no
> answer to the oplock request, and ok, WIN98ME Clients will hang sometimes,
> but on one share I run a dos database Software (Cobol), and when there is
an
> oplock problem all clients hang and most time I have to restart samba.
> Is there any one who knows what I can do?
The Windows 9X line seems to have a lot of trouble with oplocks. You may want
to turn oplocks off altogether.
YOu can also try the "veto oplock files" parameter in smb.conf to turn
off
oplocks only for the files that seem to be causing problems.  Personally, I
think this is more work than it's worth, since any files that would be
causing
trouble with oplocks will be the same files that would benefit from oplocking,
so why go to the trouble and time of identifying them when you can just turn
it off altogether.
My understanding is that this is a windows bug, Windows 9x has buggy oplock
code, while NT/2000 works OK with oplocks.  Anyone more in the know on this,
feel free to correct me if I'm wrong.

-Bill

-- 
"Where's the robot to pat you on the back?"