I already did increase the value to 12, which didn't seem to help and seemed to make the problem computers take longer. I can try raising it higher if that will help.

What are the disadvantages of running with oplocks disabled?

"Muhlestein, Mark" wrote:

Have you tried increasing the cifs.oplocks.opendelta parameter? If not, you might try a value like 16 or even 20 to see if it makes a difference. That is a hidden option which works around a bug in certain NIC/driver client setups. It is a timing issue which is seen if the server responds too quickly with an oplock break after a file is opened. The problem is not frequently seen with NT server because it is so much slower when handling opens.

Mark Muhlestein -- NetApp CIFS engineering

-----Original Message----- From: Matt Graham [mailto:mgraham@resgen.com] Sent: Tuesday, April 03, 2001 7:01 PM To: toasters Subject: oplock problems

Hello,

I have been having oplock break time outs, and I can't seem to isolate the cause of the problem. It is only certain clients that are experiencing the problem. One of the clients seemed to be fixed when I moved it from the switch that it was on to a hub (which doesn't make any sense, and may be coincidental)

Also, I never noticed these problems before we converted to a fully switched network

The clients are win98 and nt4. I am running NetApp Release 5.3.6R2.

I am now running with oplocks disabled, but it seems like a poor solution to me.

Any help appreciated, Matt