Help Center>
Elastic Volume Service>
FAQs>
Capacity Expansion>
Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?
Updated on 2024-05-27 GMT+08:00
Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?
After expanding disk capacity on the management console, you must log in to the server and extend the disk partition and file system for the extra capacity to become available. Otherwise, you cannot view the additional space on the server.
Parent topic: Capacity Expansion
Capacity Expansion FAQs
- Can I Reduce or Temporarily Expand the Disk Capacity?
- What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS Disk?
- Will My Disk Data Be Lost After I Expand the Disk Capacity?
- Can I Use Backups or Snapshots Created Before Capacity Expansion to Restore Data on Expanded Disks?
- Do I Need to Restart the Server After Expanding the Disk Capacity?
- Do I Need to Detach an EVS Disk Before Expanding Its Capacity?
- What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?
- How Can I Allocate Newly Added Space to a New Partition?
- How Can I Allocate Newly Added Space to an Existing Partition?
- Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?
- Why Can't I Expand Capacity for My Disk?
- How Do I Extend the File System of an Unpartitioned Data Disk in Linux?
- How Do I Extend the Root Partition of a Quickly Provisioned BMS?
- How Do I View the Disk Partition Style in Linux?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore