OneFS 8.2.2 and later versions fully support large files up to 16 TiB for general use on a cluster. As such, there are no limitations around client I/O access patterns, protection levels, or sparseness for large files. Furthermore, the full suite of OneFS data management and protection features is fully compatible with large files.
In general, performance for files larger than 4 TiB is comparable to other OneFS file sizes. An exception may be a small read performance impact when a large file is explicitly configured for random access (that is, isi set -a random <large_file>).
When large file support is enabled on a cluster, OneFS performs as expected up to the recommended 85 percent maximum fill threshold, regardless of whether the file system is consumed by large files or a mix of file sizes.
Similarly, there is no performance impact to files smaller than 4 TiB or to clusters with large file support configured that do not contain ﬁles larger than 4 TiB. There is also no noticeable impact to restriping jobs or other job engine jobs.
Note: For any files containing an associated alternate data stream (ADS) or resource fork, while the file data may be up to 16 TiB, the maximum size of the ADS remains at 4 TiB.