Where is my LucidLink folder and data?

LucidLink Filespaces shows up for the user and application convenience as a mount-point that is generic for each operating system. This allows for a lot of collaborative setups to utilize the same path to resources across different users.

For a particular user or application workflow you can relocate your Filespace folder mount-point within the user space. Please reference this article on how to change your Filespace location. 

Windows: a Quick Access link is available within Explorer.

L:\

macOS: a Favourites link is available within Finder.

/Volumes/<filespace>

Linux: a Lucid mount-point is available on the Desktop.

/media/<filespace>

Filespace cache and file index metadata "root-path" and "config-path" locations are located by default in the user profile or home folders as hidden ".lucid" subdirectories depending on the operating system. 

To clean up after uninstallation please follow this article.

Inside the .lucid folder you will find your log files, configuration files and individual subdirectories for each Filespace previously connected. 

Each Filespace has a unique identifier {fsuid} and will be represented as its own folder containing the metadata and cache data. 

You can identify your Filespace unique identifier via Lucid CLI:

lucid status

Every Filespace client has a unique node ID and must not be duplicated. Node IDs are assigned by the Filespace service at initial connection and automatically increment as each additional client connects. 

The {fsuid}\node.cfg file contains the unique node information. Under no circumstances should a {fsuid} be migrated to a separate machine, backed up and restored, and/or a machine cloned in the case of cloud compute.

Any virtual machine (VM) snapshot or cloud compute instance that is packaged up as a template image must have the {fsuid} location purged before image creation. We cannot stress this enough, do not duplicate intentionally or accidentally node IDs, their metadata or file cache data.

The LucidLink client root-path and config-path can also be relocated to a specific disk. Please reference this article for details.