[Samba] linux_set_kernel_oplock: Refused oplock on file.
F_SETLEASE semantic problem ?
Volker.Lendecke at SerNet.DE
Thu Jun 15 10:01:56 GMT 2006
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
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba/attachments/20060615/cbbf3384/attachment.bin
More information about the samba