Samba and NFS server on same system using same filesystems

Volker Lendecke vl at
Sun Dec 11 09:59:38 UTC 2016

On Fri, Dec 09, 2016 at 10:45:55AM -0800, Yogesh Kulkarni wrote:
> There are multiple issues here.
> 1. Oplocks and leases vs delegations is definitely one of them.
> In simplest of scenario, the oplock/lease/delegation scenario occurs over
> same file, same node and kernel oplocks might kick in.
> However, I wonder what happens over a cluster ? NFSv4 asks for a delegation
> over Node1, and windows client asks for an oplock on node 2.
> AFAIK, there is no clustered integration between NFSv4 and Samba.
> Perhaps is NFS-Ganesha + CTDB + Samba the answer ?
> 2. Byte range locks
> 3. Authentication and authorization ( AD, LDAP on the same share and
> combination of thereof ) and ACL's.
> 4. NFSv3 - clients, opens being a nop, a known FH to read/write without any
> regards to caching/locking
> 5. SMB create ( open ) does too many things that need addressing ( e.g
> delete on close ) and perhaps nfs has similar mechanisms.

Sure -- once you go into the details, proper interoperability between
SMB and NFS is not solved at all. But on the other hand this works
fine for practical applications in many places as long as there is no
real concurrent access. That's why it is important to look at the
exact workload.


More information about the samba-technical mailing list