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

[Leonid Zeitlin]

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?

Thanks,
  Leonid


"Jeremy Allison" <jra at samba.org> ???????/???????? ? ???????? ?????????: 
news:20060425112121.GA14986 at linux.lan...
> On Mon, Apr 24, 2006 at 05:14:14PM -0400, mrosamba at eastgranby.k12.ct.us 
> wrote:
>> I recently upgraded from samba 3.0.10-1.fc3 to 3.0.21b-2 running on FC5.
>> Today was the first day of a typing class which uses the network version
>> of Mavis Beacon Typing which depends on file sharing.
>>
>> The users are hanging and then getting an error message during logging
>> into the product.  In /var/log/message, I can see the following message
>> for each user similar to:
>>
>>
>> [2006/04/24 09:45:24.177906, 0] smbd/oplock.c:oplock_timeout_handler(375)
>>   Oplock break failed for file mavis/Mavis15EEVNet/Mav15UserData/Ali
>> Johnson.rec -- replying anyway
>>
>> Each user has a different filename for the above message.
>>
>> Below is the smb.conf share.  Note the force user.
>
> I would suggest upgrading to 3.0.22 as there were some fixes
> in this area.
>
> Jeremy.
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba
>