Does disabling "strict locking" cause a problem if one user is writing to the file from the local host and another user is writing to NFS via the samba share at the same time?
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy Allison Sent: Saturday, October 01, 2011 6:57 PM To: Volker Lendecke Cc: '[email protected]'; Jeremy Allison Subject: Re: [Samba] strict locking and kernel oplocks in the smb.conf On Sat, Oct 01, 2011 at 08:29:03AM +0200, Volker Lendecke wrote: > On Fri, Sep 30, 2011 at 04:44:17PM -0700, Jeremy Allison wrote: > > On Fri, Sep 30, 2011 at 04:39:18PM -0700, Philip Ong wrote: > > > No other process is accessing it. So any idea why it would work fine > > > without > > > "strict locking = no" in previous kernels below 2.6.36.3? > > > > When "strict locking = yes" we make fcntl() locking query calls > > to make sure we're safe against existing POSIX locks. > > > > The NFS locking code is probably just broken. > > I think you're talking about "posix locking = yes/no". Well yeah, but "strict locking" will map onto posix locks underneath if "posix locking = yes", which it is by default. So I still think it's the underlying POSIX locking on NFS that's probably broken and causing this :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
