similar to: Oplocks Usage Recommendations Whitepaper (with attachment)

I have written a whitepaper for CIFS/9000 Server (Samba on HP-UX) that discusses some rudimentry usage recommendations for oplocks. Due to the recent discussion about oplocks on the list, I have edited the paper to be more generic for Samba on HP-UX and converted it to plain text. It's still 7 pages long, so it may be inappropriate to paste into an email. If there is any interest in it, I

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

jiva, in some ways this question, or at least the answer, is best seen on samba@samba.anu.edu.au not just on samba-technical. i don't recieve the samba digest, so don't know if you've posted it there. so. question. by "workstation" in paragraph 4, do you mean the "workstation smb client-side cacheing, which means opportunistic locking" or do you mean "the

kernel oplocks (G) 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. Kernel oplocks support allows Samba oplocks to be broken whenever a local UNIX process or NFS operation accesses a file that smbd has oplocked. This allows complete data

I thought I had things figured out, but guess not. I have multi-user Quickbooks databases that functioned fine on a Novell server but are behaving badly on a Samba share. I have created a separate share for the Quickbook databases, users are running Win XP Pro, latest patches, and the Quickbooks application installed on the desktop. It is a multiuser version. Server is RedHat ES 3, Samba

Hi! I was hoping someone had seen this problem, and might be able to help me out with it; I've tried the suggestions I found in the mailing lists and on web sites, to no avail. I'm running samba 3.0.2 on RHEL 3, and XP clients seem to occasionally have problems saving the roaming profile, resulting in error messages and the use of the local profile. The problem is when renaming

Hello, I am running a Samba 3.6.3 fileserver on Ubuntu 12.04. It is joined to a Samba 4 Active Directory domain for user authentication. I have shares configured as follows: [MyShare] path = /path/to/MyShare browseable = yes public = yes guest ok = yes writable = yes printable = no create mode = 0664 force create mode = 0660 directory mode = 0775 force directory mode

I noticed that the Release Notes for Samba 3.0.21 say that the oplock implementation has been rewritten. And we seem to be having problems with some .exe files we are sharing out as read-only shares. The shares now only allow the first person to open the executable and run it. Other users time out with a memory address error. Do I need to specify some new oplock option for these shares now? I

Dear Alexandre, this problem of data-corruption with file based databases is not a Dataflex issue, nor is it necessarily a Samba issue. The problem basically is that when an application tells windows to write data to a file, the data is normally not written directly to the file but placed in a cache. Windows then waits till it has some free time and then proceeds to write the data to the storage

Hi Volker Thanks for your quick answer. Now I upgraded samba to 3.0.32 but this didn't fix the problem. We have three other servers with freebsd and samba in our environment. I also compared the settings and the only difference I can find is that on this server with these problems is the acl support disabled because we had some problems with it. May this acl support have something to do

phl@cyways.com wrote: > > >From the Samba 2.0 beta announcement: > > 5). Cross protocol data integrity > --------------------------------- > > An open function interface has been defined to allow > "opportunistic locks" (oplocks for short) granted by Samba > to be seen by other UNIX processes. This allows complete > cross protocol (NFS and SMB) data

You wrote: | The problem that I'm having is that once a file has been opened from the | share, changes made to that file via the WWW interface are not seen by | the Win95 client, they still get the old file's contents. This is an artefact of the so-called ``opportunistic lock'' algorithm, which allows client-side caching unless another pc client attempts to edit the file. You

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

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,

Greetings All, I am trying to turn off oplocks and can not seem to figure out which parameters to use. I have tried setting oplocks = False in both the global section and in my share section. I have also tried setting veto oplock files = /*.txt/ in my share section. Each time I try this and restart the smbd program I get the same behaviour on the PC side. The file is cached on the PC side (I

Hello, We are running into the problem in slower performance on oplock. Here is the oplock scenario. - We are using 3.0.22. - Kernel oplock has been implemented on hp-ux 11v3. - smb.conf kernel oplocks = Yes oplock break wait time = 0 fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = Yes oplock contention limit = 2

Since switching from Samba 2.2.3a-6 on Debian stable to 3.0.2a packages from the samba.org server (system is Debian stable too) we've had extreme problems with Office documents. Samba acts as a PDC and the user log onto it. The LDAP Authentication works great. Our clients are all Windows 2000 and Office 2000. When opening documents word (excel) sometimes just hangs (for 30 seconds until

Hi guys I have that config in global section of smb.conf: kernel oplocks = No locking = Yes oplocks = No level2 oplocks = No strict locking = No veto oplock files = /*.pdf/*.PST/*.pst/*.doc/*.xls/*.docx/*.mdb/*.MDB/*.dbf/*.DBF/*.ppt/*.xlsx/ I restart the service and I am still getting that log: [2010/12/23 11:16:24.105806, 5]

I've modified the contention limit in attempt to troubleshoot this, thinking that perhaps the client may be requesting multiple oplocks for whatever reason. The client is still not getting an oplock without specifying 'fake oplocks = yes'. I'm open to any ideas for troubleshooting. I've also checked to see if oplocks are explicitly disabled on the client, and they are not.

In order to deal with bizarre MS Office junk, it looks like I may have to disable oplocks on my samba server. What kinds of problems, if any could arise from my having disabled the oplocks? Alex Laslavic Havertys Tech Services