Developer(s) | Isilon Systems |
---|---|
Full name | OneFS |
Introduced | 2003FreeBSD | with OneFS 1.0 -- based on
Structures | |
Directory contents | B+ trees |
File allocation | B+ trees |
Limits | |
Max volume size | 66PB+ (144+ nodes at 470TB+ each);[1] 65535 nodes theoretical limit |
Max file size | 16TB |
Max no. of files | Cluster size dependent |
Max filename length | 255 bytes |
Max directory depth | 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. |
Features | |
Dates recorded | Create time, rename time, mtime, ctime, atime |
Date range | 1970 to 2038 |
Date resolution | Nanosecond |
Forks | Yes (extended attributes and Alternate Data Streams) |
File system permissions | Yes (POSIX permissions and NTFS ACLs) |
Transparent compression | Yes[2] |
Transparent encryption | Integrated with Self-encrypting Drives for encryption of "data at rest"[3] |
Data deduplication | Offline only |
Copy-on-write | Yes (for snapshots) |
Other | |
Supported operating systems | OneFS |
The OneFS File System is a parallel distributed networked file system designed by Isilon Systems and is the basis for the Isilon Scale-out Storage Platform.[3] The OneFS file system is controlled and managed by the OneFS Operating System, a FreeBSD variant.[3]
h8202-onefs
was invoked but never defined (see the help page).