Fw: Op-lock bug in 2.2.2 ?

[Andreas Moroder]

Sorry for the log question.
There was a little typo in my smb.conf, log.smb has another name

I found the following warnings in the logfile

[2001/10/24 06:54:04, 0] smbd/oplock.c:oplock_break(786)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file informatik/bwclient/bwclient.exe (dev = 811, inod
e = 921604).
[2001/10/24 06:54:04, 0] smbd/oplock.c:oplock_break(859)
  oplock_break: client failure in oplock break in file informatik/bwclient/bwcli
ent.exe

Bye
Andreas


> 
> > 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.
> 
> 



--------------------------------------------------------
Dr. Andreas Moroder
Sanitätsbetrieb Brixen - Azienda Sanitaria di Bressanone