Skip to main content
Version: 3025.10

Introduction

Welcome to the documentation for Fusion SMB. This section orients you with the product capabilities and highlights what comes next in the guide.

Getting Started​

Use these resources to plan your deployment before diving into the detailed configuration and operations content.

What’s new in Fusion SMB 25Q4 Major Release (Version 3025.10)​

The Fusion SMB 25Q4 major release is now available and contains our latest features for improved performance, scale, reliability, and management. It builds on our commitment to enterprise production services you can trust. Tuxera creates two major releases of Fusion SMB annually, in the 2nd and 4th quarter of each calendar year. There are also two maintenance releases, in the 1st and 3rd quarter. Below is a summary of what’s new, with links to further details and configuration guidance.

Package-based binary deployment​

Tuxera now offers eval and production Fusion SMB server binaries in standard deb and rpm packages for installation using common package managers like apt and dnf. Installing a package also automatically configures the service and creates a basic conf file which you can then manage with tsmb-cfg, significantly simplifying the deployment and configuration process. We still provide standard tar packages for customers. For more information, review the updated setup instructions.

Recycle bin for SMB shares - Fusion SMB​

Fusion SMB server now supports moving files deleted from the share to a temporary recycle bin. This behavior is not dependent on the client OS and if the Recycle Bin location is specified within a share, users can view, restore, and permanently delete files. This feature must be enabled by an administrator. For more information, review the recycle bin feature description.

Full support for opportunistic locks and leases in scale-out mode​

SMB 2 and later grants opportunistic locks (oplocks) that allow clients to cache data and file handles. By reducing the number of operations, the Fusion SMB server gains increased client capacity and scale, reduces network consumption, and allows better client application response time. Fusion SMB server has always automatically supported oplocks and leases in standalone and active-passive cluster mode, and now also when operating in scale-out cluster mode.

Improved support for Active Directory forests with many domain controllers​

Fusion SMB now decreases the number of LDAP ping and TCP connection attempts to reduce overall time used for mapping domain controllers and trusted domains. The time allowed for establishing LDAP TCP connections is also reduced before timeout. Fusion SMB also breaks up LDAP ping messaging to smaller batches of requests during domain controller discovery when there are many DCs. Furthermore, Fusion SMB now uses LsarLookupNames and LsarLookupSids RPC calls for resolving SIDs of accounts from trusted domains for which the domain controllers are not accessible. Previously, a very large number of domain controllers, trusted domains, and inaccessible domain controllers could delay the Fusion SMB service start time and certain operations.

Site awareness for LDAP/Kerberos services​

Fusion SMB now attempts connections to LDAP servers in order of priority as defined by the 'priority' field of the DNS SRV resource record and follows Active Directory site awareness rules for closest domain controllers. Previously, the first domain responding might not be one optimal to the Fusion SMB server.

Support TLS binds with non-AD LDAP servers​

Fusion SMB now supports LDAPS bind (i.e. with TLS) for a more secure connection to a native LDAP server, such as OpenLDAP.

Track cumulative bytes written/read per-connection with tsmb-status​

The tsmb-status tool now outputs cumulative bytes written and read for each client connection’s total duration, through the “data bytes” fields. For example:

    {
      "Name": "SMB Read",
      "Count": 0,
      "Total duration": "0.000000000",
      "Data bytes": 0
    },
    {
      "Name": "SMB Write",
      "Count": 49757,
      "Total duration": "352.716783288",
      "Data bytes": 104347992064
    },

These differ from the existing "RX bytes" and "TX bytes" fields, which contain overall bytes of all packets including SMB2 header. "Data bytes" are only the payload of READ and WRITE.

Option to manually specify cluster node instance-ids​

To guarantee the uniqueness of Fusion SMB identifiers across a cluster, each node file server needs a different seed for generating them; this is assigned automatically by the cluster engine. When replacing a a supported cluster engine with one that doesn’t automatically assign IDs, you can now control the seed parameter with a new command-line option. For more information on setting this value, review the -i <intance-id> parameter description.