Help Center
Elastic Volume Service
Product Introduction
Overview
Terms
Product Advantages
Product Features
Product Specifications
Disk Type and Performance Description
List of Supported Host Specification Families for Mounting
Scenario
Security
Billing Descriptions
Billing Modes
EVS Billing Description
EVS Snapshot Billing Description
User Guide
Scaling up EVS
Overview of Scaling up EVS
Scaling Up Partitions and File System (Windows 2008)
Scaling Up Partitions and File System (Windows 2016)
Scaling Up Partitions and File System (Linux)
Mounting EVS Containing Data
Mounting Non-shared EVS Containing Data
Attaching Shared EVS Containing Data
Unmounting EVS
Initializing a Data Disk
Scenarios and Precautions
Initializing a Windows Data Disk
Initializing a Linux Data Disk
Unsubscribing from Data Disks in Yearly/Monthly Subscription Mode
Deleting EVS in Pay-As-You-Go Mode
Viewing EVS Details
Managing Volume Backup Service
Managing Shared EVS Disks
Viewing EVS Monitoring Metrics
Managing Quota
Changing EVS Quota
Modifying EVS Name
EVS CTIAM
Appendix
Setting the EVS Release Policy
Quick Start
Status Description of EVS
Preparation
Create EVS
Mounting EVS
Initialising EVS
Introduction to Naming of a Linux-based Data Disk
Initialising Windows-based Data Disks (Windows 2008)
Initialising Windows-based Data Disks (Windows 2019)
Capacity Greater than 2 TB, Initialising Windows-based Data Disks (Windows 2008)
Initialising Linux-based Data Disks
Initialising Linux-based Data Disks (parted)
Capacity Greater than 2 TB, Initialising Windows-based Data Disks (Windows 2012)
Capacity Greater than 2 TB, Initialising Linux-based Data Disks (parted)
Best Practices
Managing Elastic Volume Service Using LVM
Creating EVS Using LVM and Formating File System
Creating Resources
Expanding the Capacity of Logical Volumes with Unallocated Capacity
Expanding the Capacity of a Logical Volume by Expanding EVS Capacity
Building RAID Arrays using EVS
Addressing the Problem with Insufficient Space of Windows-based ECS
Addressing the Problem with Insufficient Space of Linux-based Cloud Server
Expanding EVS Capacity to Greater Than 2 TB, Switching MBR Partition to GPT Partition
Configuring UUID in the fstab File to automatically Mount Data Disks
How to Test the Performance of EVS
FAQs
General FAQs
Billing FAQs
Mounting and Unmounting FAQs
Scaling up
Unsubscription and Deletion FAQs
EVS Backup FAQs
Agreements
eSurfing Cloud Elastic Volume Service Agreement
Help Center
Elastic Volume Service
Best Practices
Addressing the Problem with Insufficient Space of Linux-based Cloud Server
Addressing the Problem with Insufficient Space of Linux-based Cloud Server
2024-10-31 09:03:21
share
Weibo
Copy link
Weibo
Copy link Weibo Copy link