Help Center>
Bare Metal Server>
FAQs>
Disk FAQ>
Why Is the EVS Disk Size Not Updated in the BMS OS After the EVS Disk Capacity Has Been Expanded?
Updated on 2022-07-13 GMT+08:00
Why Is the EVS Disk Size Not Updated in the BMS OS After the EVS Disk Capacity Has Been Expanded?
If this occurs, scan block devices in the BMS OS. Take the sdh disk of Red Hat as an example, run the echo 1 > /sys/block/sdh/device/rescan command.
Parent topic: Disk FAQ
Disk FAQ FAQs
- Can EVS Disks Be Attached to BMSs? How Many Data Disks Can Be Attached to a BMS?
- What Are the Restrictions for Attaching a Disk to a BMS?
- How Do I Know Whether EVS Disks Are Available in a Flavor?
- How Do I Change the Disk Identifier in the fstab file to UUID?
- How Do I Obtain the Drive Letter of an EVS Disk?
- Are the EVS Disk Device Names on the Console and the Device Names in BMS OSs Consistent?
- Why Is the EVS Disk Size Not Updated in the BMS OS After the EVS Disk Capacity Has Been Expanded?
- How Can I Restore System Disk Data Using the Snapshot?
- What Do I Do to Prevent Risks of Attaching or Detaching the System Disk?
- How Should I Select Storage?
- Why Is the Disk Capacity Displayed in the BMS OS Less Than That Displayed on the Official Website?
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