similar to: Can I have oplocks enabled without problems?

I am using this command: #rsync -tr /home/ndemou/test/ /media/MOB1/m/test/ /home/ndemou/test/ has only one file named "1" (without the quotes) /media/MOB1/m/test/ is empty and it's on a vfat partition mounted as #mount /dev/sda1 /media/MOB1/ -t vfat -o iocharset=utf8,umask=000 The file 1 is created at the destination but I get this error "failed to set times on

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

I'm using samba version 2.2.1a on a linux RH7.2 kernel 2.4.7-10. I'm having a lot of oplock problems, specially when using office applications like word. I would like to know: 1. what is the recommended configuration in version 2.2.1a (oplocks = yes/no , level2 oplocks = yes/no , kernel oplocks = yes/no) 2. what is considered to be a stable version for oplocks usage Thanks, Nir

Hello all, Either the docs or the value in smb.conf.default is wrong. (Or at least confusing).

I have been searching for info on this and haven't found an authoritative answer. From what I have read, oplocks are good because they increase connection speeds, but they are bad because they don't really work, but they actually do work, but they only work in some cases, etc etc. so, here's my problem and my question together: I get tons of these messages every day (over a thousand a

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,

Hello, I'm wondering just how critical it really is to turn off oplocks. It appears that not only Windows 2k server, but also Netware 5 and above defaults to having these enabled. I just spoke with two software companies running databases off of file servers (no database server, just MDAC stuff), and they had never heard of it, much less require it to be disabled. Everything I've

Robert Dal Santo wrote: > 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 application > to perform decently. The application in questions takes around 5 > hours to do a taks without OPLOCKS and around an hour to do the

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

Hello! When I'm set oplocks to Yes I'm getting "Oplock break failed for file %s" and files (.doc .xls and .jpg|png etc) take forever to load When I set oplocks to No files opening o.k. but MS Word is saying that they are Read Only. Permissions are 100% fine. The client is Windows 7 Enterprise. Please help.... this is so important to me :( Was it resolved in SAMBA

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

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' m experiencing many problems with oplocks break failure and Error: no route to host.essentialy onto \profiles dir and \netlogon dir. So My clients cannot update many files on the SAMBA/PDC and cannot read the NTconfig.pol file to update their policies. I have many PC that are old computers with Win2k and have an Antivirus and are slower machines ... This problem less occurs on newer

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 googled around and the general wisdom seems to be that oplocks provide a performance gain if files are accessed by a single client at a time (that is, if the oplock does not break). What I can't figure out is what test can show this performance gain. I mean, theoretically, document-editing applications (Word,excel) save and load whole files and hence do not benefit from oplocks.

About two months ago our sysadmin upgraded to samba 2.2.7 and we have not had any oplock problems since. A heartfelt thanks from the University of Wisconsin in Madison to the Samba team for all their hard work. If our hundreds of users understood what was going on behind the scenes, they'd be thanking you too. --- Sam Barasch Computer Systems Support Department of Biostatistics

Hi there, Can somebody please explain to me why Samba 3 requires 'oplocks = no' on shares for programs like Quickbooks to operate properly with multiple users, where Samba 2 didn't? Without this option, Quickbooks will complain about file corruption when a second user tries to open a file. This option, however, makes the particular share that the option is present in _very_ slow

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

Hello, I am having (weird) issues with XFS, in that open(...) on certain files takes 45 seconds to return. After the file has been opened, the next file in the same directory takes 45 seconds. If the file was recently opened it returns immediately. I have raised this on several mailing lists, see: <http://lists.luv.asn.au/wws/arc/luv-main/2008-06/msg00143.html>

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