Distributed File Storage delivers high write speeds, high IOPS for datapath-related operations, as well as higher read speeds in cases where block size and queue depth are low. Distributed File Storage is ideal for operations that require a lot of synchronization between Pods, and performance bottlenecks caused by contention are minimized.Documentation Index
Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
Use this file to discover all available pages before exploring further.
Features
Encryption
All data stored in Distributed File Storage volumes is automatically encrypted at rest using AES-XTS 256-bit encryption with FIPS 140-3 validated encryption keys. Encryption is enabled by default with no configuration required. Encryption keys are automatically generated and managed by VAST and are applied at the cluster level. Keys are not accessible to users or operators. Distributed File Storage does not currently support encryption for data in transit between pods and the storage backend..snapshot folder
Every Distributed File Storage volume features a folder called .snapshot, which contains a snapshot in time of the volume. This folder is accessible in any directory on the volume.
Snapshots of Distributed File Storage volumes are taken every 6 hours, and persist for 72 hours.
Trash directory
The trash directory allows asynchronous deletion of files and folders in bulk. Serialrm -rf on large directories is a slow and possibly blocking operation; moving files marked for removal to the trash folder (.vast_trash) is much faster. For more information, see Delete Files with VAST trash.
Filename conventions
Distributed File Storage accepts POSIX-valid filenames, including names that contain characters such as: and *. Applications that generate ISO-8601 timestamps (for example, 2026-04-21T14:30:00.log) or other filenames with special characters work without modification.
The / character is reserved as the path separator, and filenames cannot be empty.