SCIENTIFIC-LINUX-USERS Archives

October 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Samba and Oplocks
From:
Ray Van Dolson <[log in to unmask]>
Reply To:
Ray Van Dolson <[log in to unmask]>
Date:
Wed, 15 Oct 2014 06:07:01 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines) 
On Wed, Oct 15, 2014 at 08:50:06AM +0000, Werf, C.G. van der (Carel) wrote:
> Hi All,
> 
> We are in the process of transfering our fileservers to a new
> OS-version.
> 
> Installed latest OS 6.5 and the current Samba3-version, which is
> Samba 3.6.9.  Data folders are on XFS filesystem. Data folders are
> exported as NFS3-shares to an SSL-login server
> 
> Data folders are exported as Samba-shares to several different
> clients: - windows7, ubuntu, SL6x, MacOSX
> 
> Now it seems that some of the windows7-clients see files as being
> read-only because they seem to be locked.  I've read a lot of
> different info about file locking in Samba, but information seems
> very confusing.
> 
> So,my question is, considering the environment of mixed clients over
> CIFS and NFS, what is the preferable Samba-setting for locks,
> Kernel_oplocks, Oplocks etc ?
> 
> If anyone has a lot of samba experience, please share your thoughts
> on this subject.
> 
> Regards,
> Carel van der Werf

This has been discussed a few times on the Samba mailing list.

My recommendations are to disable oplocks and level2 oplocks explicitly
at the global level.

In some cases you'll want to disable posix locks at the share level.

Ray

ATOM RSS1 RSS2