Starting with version 4.14 Samba provides core infrastructure code that allows basing all access to the server's filesystem on file handles and not on paths. An example of this is using fstat() instead of stat(), or SMB_VFS_FSTAT() instead of SMB_VFS_STAT() in Samba parlance. Historically Samba's fileserver code had to deal a lot with processing path based SMB requests.

Current clustered Samba uses its homegrown distributed database "ctdb" as a storage backend for maintaining coherent fileserver state. ctdb predates most cloudy distributed NoSQL databases that came to rise on the wings of the likes of Google Bigtable, Amazon Dynamo, Apache Cassandra and so on in the 2000's. It has worked extremely well for the high performance scaleout NAS usecase, but the emerging shift to the cloud entails serious scalability, elasticity and managability challenges. So are there alternatives to ctdb?

This talk is going to give an overview of recent changes in the Samba fileserver and an outlook on the development roadmap. There are many things the Samba fileserver development team has on its todo list and this presentation will give a first hand insight into the making of the next Samba versions.