[Samba] Re: oplock not working correctly

Jeremy Allison jra at samba.org
Thu Apr 27 15:07:31 GMT 2006

On Thu, Apr 27, 2006 at 04:47:51PM +0200, Iain wrote:
> Jeremy Allison wrote on 04/27/06 16:15 (US date format):
> > On Thu, Apr 27, 2006 at 01:21:18PM +0200, Iain wrote:
> >> I posted a problem with oplock previously, but am guessing it goto lost
> >> in an earlier thread with the same subject line, so here goes another shot:
> >>
> >> Using Samba 3.0.22 on a Gentoo box (kernel 2.6.15) I've a situation
> >> where file locking does not seem to be functioning as expected, in that
> >> more than one user can open and write to a file without any
> >> notifications being displayed about the file already being opened by
> >> another user.
> >>
> >> In the debug output below I have two Windows XP clients accessing the
> >> same shared file, neteng02 has the file open. neteng-vm3 then opens the
> >> same file, receiving no warnings about the file being open by another
> >> user. File is modified by neteng02 and saved and remains open. File then
> >> modified by neteng-vm3 and saved. File closed and opened by neteng02 who
> >> sees only modifications made by neteng-vm3.
> > 
> > Can you try adding "kernel oplocks = no" to the smb.conf ? I've had
> > a report that the Fedora Core 5 kernel has broken kernel oplocks and
> > I'm trying to find out if this is a Fedora specific problem or in the
> > general kernel.org code.
> > 
> > Jeremy.
> Okay, logged out, changed global config setting to "kernel oplocks =
> no", restarted Samba and logged in again. Symptoms persist as before.
> Would you like me to post another debug output from the two logfiles?

Log a bug at samba.org bugzilla with the debug level 10 logfiles
from the 2 clients, the ethereal capture traces and info on the
Windows application you're using. I'm assuming you've tested against
a Windows server ?


More information about the samba mailing list