|Developer(s)||Silicon Graphics Inc.|
|Directory contents||B+ trees|
|File allocation||extent based|
|Max. volume size||17 exabytes|
|Max. file size||8.5 exabytes|
|Max. filename length||255 bytes|
|Allowed characters in filenames||All bytes except NUL|
|Forks||Yes (called extended attributes)|
|File system permissions||Yes|
|Transparent encryption||No (provided at the block device level)|
|Supported operating systems||Server: IRIX, Linux, Clients: IRIX, Solaris, Linux, Mac OS X, AIX, Windows|
A significant difference between CXFS and other distributed file systems is that data and metadata are managed separately from each other. CXFS provides direct access to data via the SAN for all hosts which will act as clients. This means that a client is able to access file data via the fiber connection to the SAN, rather than over a local area network such as Ethernet (as is the case in most other distributed file systems, like NFS). File metadata however, is managed via a metadata broker. The metadata communication is performed via TCP/IP and Ethernet.
Another difference is that file locks are managed by the metadata broker, rather than the individual host clients. This results in the elimination of a number of problems which typically plague distributed file systems.
Though CXFS supports having a heterogeneous environment (including Solaris, Linux, Mac OS X, AIX and Windows), either SGI's IRIX Operating System or Linux is required to be installed on the host which acts as the metadata broker.