Strange oplock-messages in samba-logs

Johnny Ljunggren johnny at navtek.no
Sat Jan 26 05:38:03 GMT 2002


On Fri, 25 Jan 2002 09:51:48 -0600
"Sanjiv Bawa" <sbawa at tabmaster.com> wrote:

>> I'm getting a lot of these messages in my logs:
>> 
>> [2002/01/25 16:00:07, 0] smbd/oplock.c:request_oplock_break(995)
>> request_oplock_break: no response received to oplock break request to \
>> pid 24440 on port 44511 for dev = 4809, inode = 24110
>> 
>> for dev = 4809, inode = 24110, tv_sec = 3c5156c5, tv_usec = 1a49d

> Try
> 1. Changing the NIC card. This makes it better but will not make it go away.

Hmm... I don't have problems using NFS or ftp to this machine, so the NIC is probably not to blame.

> 2. Remove all other protocols such as Netbeui, ipx if possible.
> Effectiveness of this was not seen.

I don't think NETBeui is installed on the client machines, but I'll check on that.

> 3. Dump 2.2.2 and 2.2.1. Use 2.0.7. This one WORKS! You may not be able to
> use it since it does not have all the features. But this release works WAY
> faster and has no oplock problems at all. The 222 and 221 code is very buggy
> (despite its claims) and nobody has identified the problem.

What are the main differences between 2.0.7 and 2.2.0-15?
What subversion of 2.0.7 is ok to use (ie: 2.0.7-36 from the RH 7.1 CD)?

BTW: What exactly are these oplock-problems? 

-- 
Johnny Ljunggren, Bærefjellvn 15, 3160 STOKKE
Tlf: 918 50 411, ICQ: 50630605




More information about the samba mailing list