Build 2.2.4403

Introducing fine-grained permissions

Available in all newly created Filespaces.

Fine-grained permissions feature introduces two key improvements:

• A new permissions model that addresses all the inefficiencies of the legacy “share a folder” model (see below).
• Provides a solid foundation to easily expand the product to support more granular permissions in future versions.

Key aspects:

• All users will see a consistent folder structure, regardless of any differences in the permissions they are granted.
• No more relinking in creative tools because of differences in the folder structure.
• All users will see renamed folders consistently.
• No more conflicts with identically-named folders when providing access.
• Learn more: https://lucidlink.com/kb-fine-grained-permissions.

Additional changes:

• As a part of the fine-grained permissions, the legacy term “Shares” has been changed to “Permissions.” The change in wording is a necessary complement to the change in the permissions model.
• Added a new CLI command “lucid permission”.
• Removed support for the CLI command “lucid share” in the newly created Filespaces.
• The term “Filespace format” is introduced to help differentiate the major differences in Filespaces’ internal structure. Filespace format is now visible through UI and CLI for every Filespace. Learn more: https://lucidlink.com/kb-filespace-formats.

An upgrade tool will be released in the near future to allow for existing Filespaces to be upgraded to the new fine-grained permissions model without necessitating a data migration.

Additional improvements

Also available in existing Filespaces.

• [critical] A new mechanism has been introduced to prevent both metadata and data corruption when a .lucid/ folder is unknowingly duplicated. A .lucid/ folder is vulnerable to unintentional duplication during certain typical customer IT processes. Examples of these customer processes include creating a Virtual Machine (VM) from a base image that contains a .lucid/ folder, or reverting to a VM state that contains a .lucid/ folder, or, inadvertently restoring a .lucid/ folder from a backup. When encountering a stale .lucid/ folder, the LucidLink Client will immediately pause, allowing for a reset of the local metadata and data cache on a subsequent Filespace connection. This reset represents a critical step in averting any potential corruption in the future.
• [macOS] Updated LucidLink installer wizard to reflect changes specific to macOS Ventura.
• The remote upload indicator REST API is now available. Supported for Filespace format 2.0 or above. Visit https://client-api.lucidlink.com/ for more information.
• Both used storage and file system size are now displayed in the UI dashboard.
• Consistent inode/fileId numbers now persist across different client instances, even if a file is renamed/moved by a remote client.

Bug fixes

Also available in existing Filespaces.

• Fixed a bug where the remote upload indicator might get stuck indefinitely.
• Fixed a bug where if the local metadata cache size is set to be greater than 1GB the number of files available for pinning starts to decrease.

The latest LucidLink Client version is fully compatible with all existing and newly created Filespaces.