[Samba] linux_set_kernel_oplock: Refused oplock on file. F_SETLEASE semantic problem ?

[Cedric Delfosse]

Jeremy Allison a écrit :
> On Thu, Jun 15, 2006 at 11:39:21AM +0200, Cedric Delfosse wrote:
>> (Samba 3.0.21c / kernel 2.4.27 / Debian Sarge)
>>
>> Hello,
>>
>> One of my user open a file (located on a SAMBA server) in its 
>> application, and when he tries to save it, he gets a "share violation" 
>> error. (other people have this problem too).
>> This error happens since I upgraded the SAMBA server from 3.0.14a to 
>> 3.0.21c.
>>
>> smbstatus for this file:
>>
>> 32613        DENY_WRITE 0x20089     RDONLY     NONE 
>> /home/user/J84400os-V8   Thu Jun 15 10:46:05 2006
>>
>> Samba log when trying to save the file:
>>
>> [2006/06/15 10:50:44, 2] smbd/open.c:open_file(350)
>> user1 opened file J84400os-V8 read=Yes write=No (numopen=12)
>> [2006/06/15 10:50:44, 3] smbd/oplock_linux.c:linux_set_kernel_oplock(161)
>> linux_set_kernel_oplock: Refused oplock on file J84400os-V8,
>> fd = 33, dev = b, inode = 2621998. (Resource temporarily unavailable)
> 
> You can turn off kernel oplocks with "kernel oplocks = no"
> in your smb.conf. You might want to try 3.0.22 (or the 3.0.23RC2)
> instead as we made changes in this area.

I will try 3.0.22 and tell you if this fix my problem.

Regards,

-- 
Cédric Delfosse                             Linbox / Free&ALter Soft
152, rue de Grigy - Technopole Metz                       57070 METZ
tél : 03 87 50 87 98                               http://linbox.com