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

[Cedric Delfosse]

Volker Lendecke a écrit :
> On Thu, Jun 15, 2006 at 11:39:21AM +0200, Cedric Delfosse wrote:
>> 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.
> 
> Try with 'kernel oplocks = no'. This is safe as long as you
> do not have any processes that concurrently access the files
> from Unix or via an NFS export.

Thanks, at last this can solve my issue for the moment.

But could you provide me a setup (linux kernel version/ glibc version ?) 
  where kernel oplocks works ?

(by the way, smb.conf manual say about the kernel oplocks parameters: " 
This parameter defaults to on ... You should never need to touch this 
parameter." Maybe this statement should be changed.)

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