[Samba] Re: Re: smbd/oplock.c:oplock_timeout_handler(375) aftersambaupgrade

Jeremy Allison jra at samba.org
Wed Apr 26 11:15:59 GMT 2006


On Wed, Apr 26, 2006 at 12:32:43PM +0300, Leonid Zeitlin wrote:
> 
> "Jeremy Allison" <jra at samba.org> ???????/???????? ? ???????? ?????????: 
> news:20060426062923.GC25946 at linux.lan...
> > On Tue, Apr 25, 2006 at 08:08:20PM +0300, Leonid Zeitlin wrote:
> >> Hi all,
> >> I have the same problem with Samba 3.0.22 on Fedora Core 5.
> >> In my case the users are getting timeouts when checking out files from
> >> a Visual Source Safe database located on a Samba share. The messages in
> >> /var/log/messages are the same:
> >>
> >> Apr 25 19:45:34 elephantb smbd[5155]: [2006/04/25 19:45:34, 0]
> >> smbd/oplock.c:oplock_timeout_handler(366)
> >> Apr 25 19:45:34 elephantb smbd[5155]:   Oplock break failed for file
> >> B2/data/z/zpagaaaa -- replying anyway
> >>
> >> I have oplocks and kernel oplocks parameters turned on.
> >>
> >> Is there any way to help this problem?
> >
> > Check into your network hardware/hubs/routers etc. This is
> > a common symptom of a network problem.
> >
> > Jeremy.
> 
> Hi Jeremy,
> Thanks a lot for your reply.
> Testing shows no network connection problem so far, so I think it's 
> unlikely.
> 
> A new observation: turning kernel oplocks off (while still keeping oplocks 
> on) seems to resolve the problem. Can this give a clue to the problem's 
> source?

Yes, that's a kernel bug. If a bug appears with kernel
oplocks on and doesn't with kernel oplocks off then it looks
like file leasing is broken in the FC5 kernel. What kernel
version ID does it report.

Jeremy.


More information about the samba mailing list