change oplock contention limit because corruption?

[Robert Schott]

Is there anybody in the list who can tell me the influence of the
oplock contention limit to control the locking behaviour on a shared
directory/file?

We have one file that is opened for write ops from several wkstations.
It showed, that this file is being corrupted after some write ops.

It has been told by the software manufacturer that they had under *some*
conditions similar behaviour with a Novell server. They had to disable the
write cache, there.

Is it possible to slow the server so it behaves like a - sorry - weird
Novell or NT box?

Robert




Robert Schott
rschott at roottec.com

------------------------------------------