Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
    • All guides
      • Creating a file storage
      • Attaching a file storage to a VM
      • Detaching a file storage from a VM
      • Updating a file storage
      • Getting file storage info
      • Configuring file storage access permissions
      • Deleting a file storage
    • Viewing operations with resources
    • Viewing metrics Monitoring
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. File storages
  3. Detaching a file storage from a VM

Detaching a file storage from a VM

Written by
Yandex Cloud
Updated at July 31, 2026
View in Markdown
  1. Unmount the file storage from the VM:

    1. Connect to the VM over SSH.

    2. If you previously added a line to the /etc/fstab file to automatically mount the file storage to the VM at startup (e.g., when attaching the storage to the VM), delete that line.

    3. Run this command:

      sudo umount <mount_path>
      
    4. To check that your file storage is unmounted, run this command:

      df -T
      

      The result must show no virtiofs type file system mapped to the file storage:

      Filesystem        Type         1K-blocks    Used Available Use% Mounted on
      udev              devtmpfs        988600       0    988600   0% /dev
      tmpfs             tmpfs           203524     780    202744   1% /run
      /dev/vda2         ext4          13354932 1909060  10861420  15% /
      tmpfs             tmpfs          1017604       0   1017604   0% /dev/shm
      tmpfs             tmpfs             5120       0      5120   0% /run/lock
      tmpfs             tmpfs          1017604       0   1017604   0% /sys/fs/cgroup
      tmpfs             tmpfs           203520       0    203520   0% /run/user/1000
      
  2. Stop the VM.

  3. Detach the file storage from the VM in Compute Cloud:

    Management console
    CLI
    Terraform
    API
    1. In the management console, select the folder where your file storage resides.
    2. Navigate to Compute Cloud.
    3. In the left-hand panel, select File storages.
    4. Select the storage.
    5. Go to the Virtual machines tab.
    6. In the line with the VM in question, click and select Detach file storage.
    7. In the window that opens, confirm the detachment.

    If you do not have the Yandex Cloud CLI yet, install and initialize it.

    The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

    1. See the description of the CLI command for attaching a file storage to a VM:

      yc compute instance detach-filesystem --help
      
    2. Get a list of file storages in the default folder:

      yc compute filesystem list
      

      Result:

      +----------------------+-------------------+------------+---------------+--------+-------------+
      |          ID          |        NAME       |    SIZE    |     ZONE      | STATUS | DESCRIPTION |
      +----------------------+-------------------+------------+---------------+--------+-------------+
      | epdtcr9blled******** | first-filesystem  | 1073741824 | ru-central1-a | READY  |             |
      | epd3f4gv8bs4******** | second-filesystem | 1073741824 | ru-central1-a | READY  |             |
      +----------------------+-------------------+------------+---------------+--------+-------------+
      
    3. Get a list of VMs in the default folder:

      yc compute instance list
      

      Result:

      +----------------------+-------+---------------+---------+--------------+-------------+
      |          ID          | NAME  |    ZONE ID    | STATUS  |  EXTERNAL IP | INTERNAL IP |
      +----------------------+-------+---------------+---------+--------------+-------------+
      | epdj4upltbiv******** | vm-01 | ru-central1-a | RUNNING | 51.250.**.** | 192.168.*.* |
      | 1pc3088tkv4m******** | vm-02 | ru-central1-a | RUNNING | 84.201.**.** | 192.168.*.* |
      +----------------------+-------+---------------+---------+--------------+-------------+
      
    4. Detach the file storage from a VM:

      yc compute instance detach-filesystem \
        --id <VM_ID> \
        --filesystem-id <file_storage_ID>
      

      Where:

      • --id: VM ID.

        Instead of the ID, you can specify the VM name in the --name parameter.

      • --filesystem-id: File storage ID.

        Instead of the ID, you can specify the file storage name in the --filesystem-name parameter.

      As a result, the command will output the updated VM configuration. The detached file storage must not be featured in the filesystems section of the configuration you get.

    If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

    To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

    Set the allow_stopping_for_update parameter to true on your VM, if you have not done it yet.

    1. Open the Terraform configuration file and delete the section specifying the storage:

      Example of specifying a storage in the VM configuration using Terraform
      ...
      resource "yandex_compute_instance" "vm-1" {
      
         name        = "test-vm"
         platform_id = "standard-v3"
         zone        = "ru-central1-a"
      
         filesystem {
           filesystem_id = "fhmaikp755gr********"
         }
      ...
      
    2. Apply the changes:

      1. In the terminal, navigate to the configuration file directory.

      2. Make sure the configuration is correct using this command:

        terraform validate
        

        If the configuration is valid, you will get this message:

        Success! The configuration is valid.
        
      3. Run this command:

        terraform plan
        

        You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

      4. Apply the configuration changes:

        terraform apply
        
      5. Type yes and press Enter to confirm the changes.

    You can check that the storage has been detached from the VM using the management console or this CLI command:

    yc compute instance get <VM_name>
    

    Use the detachFilesystem REST API method for the Instance resource or the InstanceService/DetachFilesystem gRPC API call.

Was the article helpful?

Previous
Attaching a file storage to a VM
Next
Updating a file storage
© 2026 Direct Cursus Technology L.L.C.