similar to: Oplocks - when do they help

Hi, I've been working with Casey Marshall's SSL patch, and couldn't get it to work reliably - the transfer would abort pretty quickly. So I rewrote the main data pump loop of the patch to use non-blocking IO, and am attaching the new patch. An rsync program using this patch is interoperable with the old patch. Along with the modified message pump I added the following improvements:

Hi We've here some problems with Samba on a freeBSD-Server. FreeBSD 6.2-RELEASE Samba Version 3.0.25a The problem is about locking of open files. For example when a user A opens a excel-sheet and a user B also opens the same file, user B won't only open this file as read-only. We moved from a Windows Server to a freebsd based one about 2 weeks ago and we also had some problems with dbs

I would like to know if like the [homes] section mapped to a single user at login time (H: drive) would have any of the problems discussed in previous emails. Specifically the oplock break issue. Since one and only one user can have this space mapped in our implementation (because of credential conflicts that windows does not allow), how could a user have a detrimental experience with oplocks?

Hi, I used to have a win NT to serve small office networks comprised of windows clients. During the last months I have made a considerable effort to learn enough about linux in order to explore it's capabilities for that application. In the area of file & print sharing samba still looks as the best choice. I am using it in my office for some weeks now and I am quite happy with it. Yet I

I've battled this one for a few days now and its costing my sanity so I am hoping that someone here has an answer I am running the samba server 3.0.4 on a linux 2.4.25 server. I can connect to my share point and authenticate fine I can create files or directories in the root of the sharepoint fine I can go into subdirectories and look at all the files... But I cannot create in any

Hello im running sage line50 version 11 on a freebsd machine with samba version 2x My smb.conf for share looks like this [sage] path = /40gb/sage writeable = yes browseable = no create mask = 0777 directory mask = 0777 veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB locking = yes share modes = yes The problem is when two users for example try and update customer records one

The kernel on my server appears to be refusing oplocks altogether. Setting 'kernel oplocks = no' resolved the issue. Is there any caveats I should be aware of? - Chris Wagner -----Original Message----- From: samba-bounces+chriswagner=amyskitchen.net@lists.samba.org [mailto:samba-bounces+chriswagner=amyskitchen.net@lists.samba.org]On Behalf Of Chris Wagner Sent: Wednesday, July 05, 2006

24.01.2023 20:09, Jeremy Allison via samba wrote: > On Tue, Jan 24, 2023 at 12:38:29PM +0300, Michael Tokarev via samba wrote: >> >> Here we've two files open, with kernel oplocks = yes (hence it is LEASE(), - >> before I enabled kernel oplocks, it was LEASE(RH) or LEASE(RWH)). > > Kernel oplocks do not support SMB2+ LEASES. So you're > just seeing old

Hello, We are running some legacy software that instructs us to, via Windows registry settings, disable all oplocks and SMB2 entirely on each Windows workstation that connects to the Samba share where the software is hosted. The software maintainers give dire warners of corruption, etc., if oplocks (and SMB2) are left enabled. We?ve run this software off of a Samba share for 20 years and have

I've tried to configure samba to lock files bewteen windows and linux but i couldn't i've read a lot of messages here, but trere is no one that have something about the file smb.conf. i have this in my global secction but i doesn't work [global] workgroup =3D GMC create mask =3D 0777 os level =3D 16 directory mask =3D 0777 hosts allow =3D

Hello, I'm trying to disable oplocks on our system. Is it sufficient to set: oplocks = no level2 oplocks = no or do I need to also set kernel oplocks = no ? What would be the effect of keeping kernel oplocks = yes if the first two are disabled. running a testparm shows that this is set to yes by default Thanks in advance, Dennis

In the documentation the "oplocks = yes" option is give in an example, as the default for this parameter. However, I needed to turn oplocks off, and so assumed that the command "oplocks = no" would work. It doesn't, instead I found that "oplocks = false" does. There needs to be some boolean fixing done, or at least documentation should reflect this strangeness.

On Tue, Jan 24, 2023 at 08:29:17PM +0300, Michael Tokarev via samba wrote: >24.01.2023 20:22, Ralph Boehme via samba wrote: >>What Samba version is this? This: >> >>>LEASE() >> >>... looks broken: the handle oplock/lease state claims to be a >>lease, which means the client didn't request an oplock but a lease >>which should not have happened in

SuSE 7.2, Samba 2.2.6 User plaform WIN98se Was wondering if someone could point me to information regarding oplocks (I read the man on smb.conf regarding that and level2 oplocks)... I needed to set oplocks = no and level2 oplocks = no in order for them to be able to open pagemaker files from the samba server...otherwise it would say 'can not open file' I am just trying to get a grip on

I am a little bit confused about the kernel support for oplocks. man page of smb.conf: ---------------- For UNIXs that support kernel based oplocks (currently only IRIX but hopefully also Linux and FreeBSD soon) this parameter allows the use of them to be turned on or off. This parameter defaults to "On" on systems that have the support, and "off" on systems that don't.

Hi, I have serious problems to manage oplocks on Samba Share. Some clients have been installed Office 2000 SP3 + Windows XP SP1; they aren't working because Word+ Excel save files only read-only when reopen the file and I try to save. If use Wordpad or something else, It'll works fine. on the smb.conf: level2 oplocks = yes oplocks = yes veto oplock files =

Hi, I have an application under Access that is running dead slow. I've done some testing and it appears that Access really likes to use OPLOCKS which of course Samba does not support. Is there any work underway to get Samba to support OPLOCKS? I know they are difficult to implement but I'm faced with a decisions now to buy an NT box (Ugh!) or do a lot of messing around to get this

Hi Can anyone advise me on "kernel oplocks" in a ctdb cluster. I have a ctdb (GPFS is the parallel file system) setup that uses samba (3.5.8) for cifs and IBM CNFS for NFS. Reading the documentation on kernel oplocks it seems to me that I can export the same area via samba and NFS with "kernel oplocks = Yes" . My logic is that IBM CNFS has shared NFS locking

Dear all, We have samba-3.0.11 on freebsd 5.4 as file/print server it works perfect, but if two users open the same file together the second still can write to the file it cannot be allowed in you situation. But the other server with freebsd 4.11 doesn't have this problem perfectly do write lock on open file, so may be it's freebsd 5.x problem? I can't find what's wrong,

I have follow ERROR Message in my log: [code] #cat samba.log.tn-ss1lxgxvomck [2004/03/21 13:34:32, 0] lib/util_sock.c:read_data(436) read_data: read failure for 45164. Error = Connection reset by peer [2004/03/21 13:39:03, 0] smbd/oplock.c:request_oplock_break(1011) request_oplock_break: no response received to oplock break request to pid 4146 on port 1031 for dev = 1601, inode = 134,