509 (suggested, to fit within PATH_MAX of 1023)[1]
Allowed filename characters
Many (UTF-8, EUC-JP, CP932, CP1252, ISO-8859-*, EUC-KR, CP949). Encoding is per-directory entry, not per-filesystem. So multiple encodings may be used in a single volume. UTF-8 is encouraged as normative. NUL and / are not allowed in individual directory entries in any encoding.
All data structures in the OneFS file system maintain their own protection information. This means in the same filesystem, one file may be protected at +1 (basic parity protection) while another may be protected at +4 (resilient to four failures) while yet another file may be protected at 2x (mirroring); this feature is referred to as FlexProtect.[4] FlexProtect is also responsible for automatically rebuilding the data in the event of a failure. The protection levels available are based on the number of nodes in the cluster and follow the Reed Solomon Algorithm. Blocks for an individual file are spread across the nodes. This allows entire nodes to fail without losing access to any data. File metadata, directories, snapshot structures, quotas structures, and a logical inode mapping structure are all based on mirrored B+ trees. Block addresses are generalized 64-bit pointers that reference (node, drive, blknum) tuples. The native block size is 8192 bytes; inodes are 512 bytes on disk (for disks with 512 byte sectors) or 8KB (for disks with 4KB sectors).
One distinctive characteristic of OneFS is that metadata is spread throughout the nodes in a homogeneous fashion. There are no dedicated metadata servers. The only piece of metadata that is replicated on every node is the address list of root btree blocks of the inode mapping structure. Everything else can be found from that starting point, following the generalized 64-bit pointers.
Clustering
The collection of computer hosts that comprise a OneFS System is referred to as a "cluster".
A computer host that is a member of a OneFS cluster is referred to as a "node" (plural "nodes").
The nodes that comprise a OneFS System must be connected by a high performance, low-latency back-end network for optimal performance. OneFS 1.0-3.0 used Gigabit Ethernet as that back-end network. Starting with OneFS 3.5, Isilon offered InfiniBand models. From about 2007 until mid-2018, all nodes sold utilized an InfiniBand back-end. Starting with OneFS 8.1.0 and Gen6 models, Isilon again offers Ethernet back-end network (10, 25, 40, or 100 Gigabit).[5]
Data, metadata, locking, transaction, group management, allocation, and event traffic are communicated using an RPC mechanism traveling over the back-end network of the OneFS cluster. All data and metadata transfers are zero-copy. All modification operations to on-disk structures are transactional and journaled.
Protocols
OneFS supports accessing stored files using common computer network protocols including NFS, CIFS/SMB, FTP, HTTP, and HDFS.[3] It can utilize non-local authentication such as Active Directory, LDAP, and NIS. It is capable of interfacing with external backup devices and applications that use NDMP protocol.[3]
OneFS Operating System
The OneFS File System is a proprietary file system that can only be managed and controlled by the FreeBSD-derived OneFS Operating System.[3]
zsh is the default login shell of the OneFS Operating System. OneFS presents a specialized command set to administer the OneFS File System.[6] Most specialized shell programs start with letters isi. Notable exceptions are the Isilon extensions to the FreeBSD ls and chmod programs.[7]
