File system limitation
The following limitations relate to the Access Appliance file system.
Any direct NLM operations from the Access Appliance command-line interface can lead to system instability
Do not perform any file system related operations using the Access Appliance command-line interface on the Network Lock Manager (NLM), as it is used for internal purposes. If NLM is used, then Access Appliance cannot guarantee the stability of the cluster.
When a file system is created, an additional file system is also created for the purpose of keeping the lock and configuration information. The additional file system is not directly accessible to the user. It is meant for internal use only.
It is recommended to use disks from as many nodes as possible when creating the first storage pool in Access Appliance. In case of a shared nothing environment where the disks are local to the cluster nodes, the additional file system mirrors are created across all those nodes. This ensures that the Access Appliance configuration is available even if one of the nodes on which the additional file system was created is available.
In case of SAN environments, the additional file system is mirrored across two disks.
On-premises tiering in a cluster file system only supports one primary and one secondary.