> ## Documentation Index > Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt > Use this file to discover all available pages before exploring further. # Create and Use Storage Volumes > After purchasing storage quota, create a Volume and mount it to a development environment, training task, or inference service. Volume is a persistent storage volume in Siverse. You can Mount a Volume to Develop, Training, and Inference to store code, data, model files, training outputs, and service dependency files. Using a storage resource typically involves three steps: first, purchase storage quota in Orders; then, create a specific Volume in Volume; finally, authorize and mount the Volume for use in workloads. ## Relationship Between Storage Quota and Volume Storage quota and Volume are two different objects: | Item | Description | | - | - | | Storage Quota | Available storage capacity purchased or renewed through orders. | | Volume | A specific storage volume created within the storage quota. It can be mounted to Develop, Training, or Inference. | Storage quota is what you purchase. Before using it, you must create a specific Volume in the Volume section; otherwise, workloads cannot mount it. After navigating to **Resources > Volume**, you can use the quota, capacity, and utilization charts at the top of the page to assess the current storage usage level: | Objective | Information to Review | | - | - | | Determine whether quota is still available | Check the usage and availability of the storage quota. | | Identify capacity distribution | Review the capacity share of each Volume to determine whether capacity is concentrated in a small number of Volumes. | | Investigate high-utilization Volumes | Review Volumes with high utilization. If necessary, adjust capacity, clean up data, or migrate data. | ## Buy Volume Volume resources must first be purchased as quotas. What you purchase is available capacity; before using it, you must also create a specific Volume. Before purchasing, please note the following information: | Item | Description | | - | - | | Minimum purchase unit | 1 Gi. | | Billing method | Billed based on the purchased capacity and number of days used. | | Quota usage | Storage quota can be used to create or expand Volumes. | 1. Go to **Resources > Order**. 2. Select the **Volume** tab and click **Buy**. 3. Configure the purchase capacity and duration. 4. Submit the purchase. 5. Return to the order list and confirm that the order status changes to `active`. 6. Return to **Resources > Volume** and confirm that the storage quota has increased. If the available storage quota is insufficient, first purchase or renew storage resources, or delete unused Volumes to release quota. For more information, see [View and Renew Resource Orders](/siverse/resources/manage-resource-orders.md). ## Create Volume After you create a Volume, Develop, Training, and Inference can mount and use the volume. Before creating, ensure that your account has permission to create or manage storage volumes and that sufficient storage quota is available in the current region and cluster. 1. Go to **Resources > Volume**. 2. On the **Quota** tab, click **Create**. 3. Configure Volume. | Parameter | Description | | - | - | | Region | The Region where the Volume resides. | | Cluster | The Cluster to which the Volume belongs. | | Name | The Volume name, which must be unique within the tenant. | | Project Group | The Project Group to which the Volume belongs. | | Public within Project Group | Controls whether the Volume is public within its Project Group. | | Directory-level Permissions | Controls whether to enable subdirectory-based authorization and mount authorization. After enabling this option, continue to configure directory permissions. | | Resource Administrator | Specify the user responsible for managing the Volume. | | Capacity | The Volume capacity. You can select the capacity unit. | 4. Click **Create**. After creation is complete, when the Volume status changes to `Ready`, you can mount the Volume in Develop, Training, or Inference. ## View Volume Status and Usage In **Resources > Volume**, you can filter volumes by Name and Project Group, and view their Status, File System Type, authorized users, resource administrators, Capacity, and Used. | Objective | Information to Check | | - | - | | Confirm whether it can be mounted | Check whether the Volume status is `Ready`. | | Determine whether capacity is sufficient | Compare total capacity with used capacity, and use the utilization chart to determine whether expansion is needed. | | Confirm the access scope | Check authorized users, resource administrators, and project group visibility. | If the Volume does not enter the `Ready` state for an extended period, verify that the order and quota are valid. If the issue persists, contact the platform administrator for assistance. If you need to use an existing Volume but your current account does not have permission, request access to the relevant volume or directory from the storage administrator. After permission is granted, refresh the creation form for Develop, Training, or Inference, and then check whether the Volume can be selected. ## Using Volumes After a Volume is mounted to a workload, applications access files through the path inside the container. The same Volume can be reused by multiple Develop environments, Training tasks, or Inference services. ### Select a Usage Scenario | Scenario | Common Use Cases | Path Recommendations | | - | - | - | | Development environment | Store code, notebooks, dependency caches, and debugging data. | Use a personal or project directory to avoid overwriting the image's default directories. | | Training jobs | Read training data and store checkpoints and output model files. | Manage input data and output results in separate directories, and write checkpoints to a writable persistent directory. | | Inference services | Mount model files, configuration files, or service dependency files. | Use a stable model directory; handle service output and runtime logs separately based on the service configuration. | ### Configure mount path When mounting, select a Volume or an authorized source directory, and specify the absolute path in the container. If directory-level permissions are Enabled for the Volume, select a subpath based on the mountable directories instead of mounting the entire volume directly. The source directory indicates the location of files in storage; the container mount path is the entry point for programs to access files within the container. For example, after mounting the source directory `/team-data/users/alice` to the container path `/mnt/work`, the path relationship is as follows: | Files in storage | Access path in the container | | - | - | | `/team-data/users/alice/data.csv` | `/mnt/work/data.csv` | | `/team-data/users/alice/checkpoints/` | `/mnt/work/checkpoints/` | When the program is running, use paths inside the container to access files. Relative paths within the underlying volume are handled by the mount configuration, so regular users do not need to construct them manually. ### Verify Read and Write Permissions When using Volume for the first time, we recommend first verifying in an approved Develop environment or Dry-run task that the directory exists and that read and write permissions meet expectations. * If files cannot be found after mounting, verify the mapping between the source directory and the container mount path. * If data can be read but not written, check whether the authorization is read-only or read-write and whether directory-level permissions cover the target directory. * If the same Volume is used for both input data and output results, separate the shared input data from the task output directory to avoid writing results to the team-shared raw data directory. ### Managing Capacity and Data Protection The remaining capacity of the Volume and the user directory quota take effect independently. If a write fails, check read/write permissions, the remaining Volume capacity, and the user directory quota. Usage statistics may be delayed due to scanning. ## Manage Volume Created volumes support the following management actions. Available actions may vary depending on account permissions, volume status, and Project Group visibility. * **Adjust**: Modify the Project Group visibility, directory-level permissions, resource administrators, or Capacity. Before adjusting Capacity, ensure that sufficient storage quota is available. * **Bulk Adjust Capacity**: Adjust the capacity of multiple Volumes in bulk. Before making adjustments, ensure that all selected Volumes require the same capacity change. * **User Authorization**: Grant users within the tenant access to a Volume and optionally set their permissions to read-only. Authorized users not set to read-only have read/write access. In private mode, if the platform needs to create underlying resources after access is granted, the changes may take several minutes to take effect. * **User Default Quota**: Use the **User Default Quota** option in the upper-right corner of the page to adjust the default quota for user directories. * **Adjust Project Group**: Modify the Project Group and visibility of a Volume. * **Delete**: Delete Volumes that are no longer needed and release the occupied quota. Deletion affects development environments, training tasks, or inference services that have mounted the Volume. Before deletion, ensure that the data is no longer needed and has been backed up or migrated. > [!WARNING] > > Persistent data must be managed in accordance with the team’s backup policy. Deleting a Volume, modifying directory permissions, and deleting actual files have different impacts. Before making adjustments, confirm the data retention and recovery plan. After authorization is revoked, old sessions or existing mounts may still require administrator intervention. Do not assume that all access has been terminated solely based on configuration changes. ## Configure Directory-Level Permissions When multiple users need to share the same large-capacity Volume but can access only certain directories within it, directory-level permissions can be enabled. Directory-level permissions support public directories, Custom subdirectories, and user directories, and can be configured with read-only or read-write permissions for different users. Directory-level permissions affect mount authorization when tasks are submitted. After this feature is enabled, configure mountable directories and authorized users on the **Directory Permissions** tab. For details, see [Configure Volume Directory-Level Permissions](/siverse/resources/configure-volume-directory-permissions.md). ## FAQ > **Why can't I select a Volume from the list when creating a task?** > > Make sure that the workload and the Volume are in the same Region and Cluster, that the Volume Status is `Ready`, and that the current account has permission to use the relevant volume or directory. If directory-level permissions are enabled for the Volume, make sure that a mount directory is available. After adjusting authorization or directory rules, Refresh the creation form and check again. If the Volume is still unavailable for selection, provide the storage administrator with the user, Volume, and directory information. > **What should I do if files cannot be found after mounting, or can only be read but not written?** > > First, verify that the source directory corresponds to the container mount path. If files can be read but not written, further check whether the authorization is read-only or read-write, whether directory-level permissions cover the target directory, and whether the remaining Volume capacity and user directory quota are sufficient. Shared input directories are generally recommended to be mounted as read-only, while output results should be written to a separate writable directory. ## Related Documentation * [Configure Volume Directory-Level Permissions](/siverse/resources/configure-volume-directory-permissions.md) * [View and Renew Resource Orders](/siverse/resources/manage-resource-orders.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.