IN THIS ARTICLE
Outlines the behaviors of Cross-Protocol Permissions in common scenarios
- Cluster running Qumulo Core 2.11.4 and above
- Admin privileges on the Qumulo cluster
Prior to the introduction of Cross-Protocol Permissions (XPP), Qumulo handled mixed protocol permissions by keeping the most recent permissions change to a file or directory. We call this “Native Permissions Mode” (previously referred to as “last chmod wins”). While this behavior is straightforward, it doesn’t solve the problem encountered in mixed-protocol workloads where collaboration can cause POSIX mode bits to unnecessarily replace SMB ACLs, and vice versa.
To simplify managing mixed-protocol permissions, we introduced the Cross-Protocol Permissions feature in the 2.11.4 release of Qumulo Core. Cross-Protocol Permissions (XPP) mode enables mixed SMB and NFS protocol workflows by preserving SMB ACLs, maintaining permissions inheritance, and reducing application incompatibility related to permissions settings.
To see how we considered the cross-protocol challenge in each common scenario and the new behavior we introduced in Cross-Protocol Permissions, check out the tables below.
MODE BIT DISPLAY
SET POSIX MODE - USER HAS RIGHTS
SET POSIX MODE - USER RIGHTS ARE RESTRICTED
OBJECT CREATION W/INHERITANCE COMPATIBILITY (NFS-ONLY)
Qumulo recommends Cross-Protocol Permissions for most customers, even those without cross-protocol workloads. The feature works transparently and automatically.
For an in-depth look at this new feature, check out the Cross-Protocol Permissions article.
You should now have an overall understanding of the expected behaviors of Cross-Protocol Permissions (XPP) in common scenarios
Like what you see? Share this article with your network!