Technical Specifications

Year 2038 Safe Yes
Timestamp Granularity 100ns (UNIX Epoch)
Rx Listener Thread Throughput <= 8.2 gbit/second
Rx Listener Threads per Service up to 16
Rx Window Size (default) 128 packets or 180.5KB
Rx Window Size (maximum) 65535 packets or 190.2MB
Rx Congestion Windows Validation Yes
Volume IDs per Cell 264
Object IDs per Volume 295 directories and 295 files
Maximum Distributed DB Size 16 exabytes (264 bytes)
Access Control Lists Per Object
Access Control Entries (ACE) per ACL > 400
Directory ACL Inheritance Yes
Volume Access Control Policies Yes
Mandatory Locking Yes
GSS Authentication (YFS-RxGK) Yes
AES-256/SHA-1 Wire Privacy Yes
AES-256/SHA-2 Wire Privacy (RFC8009) Yes
Mandatory Security Levels* Yes
Cache Poisoning Attacks Protection yfs-rxgk: Yes; rxkad: No
Combined Identity Tokens (user@device) yfs-rxgk:Yes; rxkad: No
Perfect Forward Secrecy yfs-rxgk:Yes; rxkad: No
Secure Callback Connections yfs-rxgk:Yes; rxkad: No
Default Volume Quota 20 GB
Maximum Assignable Quota 16 zettabytes (274 bytes)
Maximum Reported Volume Size 16 zettabytes (274 bytes)
Maximum Volume Size 16 zettabytes (274 bytes)
Maximum Transferable Volume Size 16 zettabytes (274 bytes)
Maximum Partition Size 16 zettabytes (274 bytes)
Servers run unprivileged Yes
UBIK quorum initial establishment 23 to 40 seconds
UBIK quorum establishment after coordinator restart 1 second
UBIK quorum establishment after coordinator shutdown <= 56 seconds
UBIK servers per cell (usable) Up to 80
UBIK voting clones Yes
UBIK non-voting clones Yes
UBIK server ranking Arbitrary order
POSIX O_DIRECT support Yes
IBM AFS 3.6 client support Yes (AFS3 protocol only)
OpenAFS 1.x client support Yes (AFS3 protocol only)
IBM AFS 3.6 DB server support Yes (AFS3 protocol only)
OpenAFS 1.x server support Yes (AFS3 protocol only)
DB Servers support AFS file servers Yes
Thread safe libraries Yes
File Lock State Callback Notification Yes
Atomic Create File in Locked State Yes
Valid AFS3 Volume Status Info Replies Yes
Server Thread Limits Up to OS capability
Dynamic Thread Pools Yes
Linux reflink aware Yes
File Server Meltdown Protection Yes
IPv6 enabled Yes
Microsoft Direct Access compatibility Yes
Kerberos Profile-based Configuration Yes

*A Security Level is defined as a Rx Security class (rxkad or rxgk) combined with cryptographic requirements for data privacy and integrity protection. Security Levels are enforced at the File Server.