Op-lock bug in 2.2.2 ?
Jeremy Allison
jra at samba.org
Tue Oct 23 11:27:04 GMT 2001
On Tue, Oct 23, 2001 at 08:25:44PM +0200, Andreas Moroder wrote:
> Hello,
>
> are there know problems with oplocks in samba 2.2.2.
>
> Since we updated our linux server from 2.0.36, Samba 2.07 to 2.4.4 and samba
> 2.2.1a
>
> we have oplock problems tiwh a shared access applications.
> Yesterday we updated to 2.2.2
>
> Now we have also BIG trouble with a application that uses the paradox
> engine.
>
> The worst is that samba seems to write no log file. log.smbd is empty while
> nmbd grwos slowly.
>
> Is it possible to set veto oplocks for entire directories ?
Can you test by turning off kernel oplocks on your Linux 2.4.x
kernel server.
Test this by setting "kernel oplocks = no" and restarting samba.
There may be a problem with the current kernel oplocks code we
need to look at.
Thanks,
Jeremy.
More information about the samba-technical
mailing list