OSS volumes support three types of clients — ossfs 1.0, ossfs 2.0, and strmvol — each optimized for different access patterns. Use this reference to select the right client before deploying an OSS volume.
Usage notes
All three clients require a minimum Container Storage Interface (CSI) plug-in version. We recommend that you upgrade your CSI plug-in at the earliest opportunity. For instructions, see Manage the CSI plug-in.
If you are unsure about your workload's read/write pattern, start with ossfs 1.0. It provides the broadest Portable Operating System Interface (POSIX) compatibility and is the safest default for general use.
Choose a client
| Scenario | Client | Documentation | Benchmark |
|---|---|---|---|
| Most workloads — read/write access or custom permission configuration | ossfs 1.0 | Mount a statically provisioned ossfs 1.0 volume · Mount a dynamically provisioned OSS volume by using ossfs 1.0 · Manage the lifecycle of OSS buckets · Encrypt OSS volumes by using ossfs 1.0 | New features of ossfs 1.0 and ossfs performance benchmarking |
| Read-only or sequential append-only workloads — AI training, inference, data processing, and autonomous driving | ossfs 2.0 | Use ossfs 2.0 volumes | Performance test for ossfs 2.0 |
| Massive small-file workloads — read-only, with infrequent updates to OSS remote data, such as training, quantization backtesting, and time series log analysis | strmvol | Use strmvol volumes | Performance testing for strmvol volumes |
| Workloads where reads and writes are separated — different paths or non-overlapping timing, such as breakpoint saving and log persistence | Split into separate volumes: ossfs 2.0 for read-only paths, ossfs 1.0 for write paths | Best practice for OSS read/write splitting | N/A |