Reallocating VM File System Capacity (Applicable to V500R007C70)

Prerequisites

A VM file system has been created.

Procedure of Reallocating the VM File System Capacity

Figure 7-1 Procedure of reallocating the VM file system capacity

Procedure

1. Optional: Power off the VM.

   If no VM is created on the VM file system, skip this step.

   1. Log in to DeviceManager.
   2. Choose VM > VM.
   3. Select the target VM and click Power Off.

      The security alert dialog box is displayed.

   4. Confirm the operation.

   If the VM fails to be powered off, perform the step as instructed in Forcibly Powering Off a VM.

2. Unmount the VM file system.

   In developer mode, run the change vm_fs general status=? vm_fs_id=? command to unmount the VM file system.

   Table 7-13 lists the corresponding parameters.

   Table 7-13 Parameters for unmounting the VM file system

   Parameter	Description	Value
   status=?	Status of the VM file system.	The value can be mount or umount, where: mount: mounts a VM file system. umount: unmounts a VM file system.
   vm_fs_id=?	ID of the VM file system.	To obtain the value, run the show vm_fs general command without parameters.

   You can run the change user_mode current_mode user_mode=developer command to enter the developer mode.

   Example:

   admin:/>change user_mode current_mode user_mode=developer 
   DANGER: You are about to switch to the developer view. Commands in this view must be run under the guidance of R&D engineers. You can choose whether to run this command. If you run this command to switch to the developer view, it means that you know risks of running commands in the developer view. Device vendors are not responsible for any loss or damage caused to the user or others by running commands in the developer view. 
   1. Running the command in the developer view may cause system reset, restart, offline, service interruption, data loss, and data inconsistency. 
   2. Running the command in the developer view may cause the performance to decrease. 
   3. Running the command in the developer view to delete or remove configurations may have impact on the service and data. 
   4. Running the command in the developer view may cause system alarms. 
   Suggestion: Run this command under the guidance of R&D engineers. 
   Have you read danger alert message carefully?(y/n)y 
   Are you sure you really want to perform the operation?(y/n)y 
   developer:/>change vm_fs general status=umount vm_fs_id=1 
   DANGER: You are about to umount the file system where the virtual machine resides. This operation may cause data to be lost and the virtual machine to be abnormal. 
   Suggestion: Before performing this operation, ensure that you want to umount the file system where the virtual machine resides. 
   Have you read danger alert message carefully?(y/n)y 
   Are you sure you really want to perform the operation?(y/n)y 
   Command executed successfully.

3. Delete the VM file system.

   In developer mode, run the delete vm_fs general vm_fs_id=? command to delete the VM file system.

   Table 7-14 lists the corresponding parameters.

   Table 7-14 Parameter for deleting the VM file system

   Parameter	Description	Value
   vm_fs_id=?	ID of the VM file system.	To obtain the value, run the show vm_fs general command without parameters.

   Example:

   developer:/>delete vm_fs general vm_fs_id=1 
   DANGER: You are about to delete the file system where the virtual machine resides. This operation will cause data to be lost and the file system to be unrecoverable. 
   Suggestion: Before performing this operation, ensure that you want to delete the file system. 
   Have you read danger alert message carefully?(y/n)y 
   Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command: 
   I have read and understand the consequences associated with performing this operation. 
   Command executed successfully.

4. Log in to DeviceManager to remove the LUN from the LUN group.
5. Delete the LUN.
6. Replan the LUN capacity and create a LUN.
7. Add the LUN to the specified LUN group again.
8. Scan the block device information in the specified container.

   On the CLI, run the scan virtual_machine block owner_container_id=? command to scan the block device information in a VM container. The owner_container_id parameter is the ID of the VM container. To obtain the value, run the show vm_container general command without parameters.

   Example:

   admin:/>scan virtual_machine block owner_container_id=1 
   Command executed successfully.

9. Check the block device information in the current system.

   On the CLI, run the show virtual_machine block command to query block device information in a system.

   Example:

   admin:/>show virtual_machine block 
     ID  Health Status  Running Status  Owner Container ID  Capacity   Use Mode  WWN                               Virtual Machine ID  Virtual Machine Name   
     --  -------------  --------------  ------------------  ---------  --------  --------------------------------  ------------------  --------------------   
     0   Normal         Online          0                   100.000GB  SYSTEM    611223310044556608923b1700000000                                             
     2   Normal         Online          1                   200.000GB  DATA      611223310044556608e7cbec00000002 

10. Create a VM file system.

    In developer mode, run the create vm_fs general block_id=? container_id=? command to create a VM file system.

    Table 7-15 lists the corresponding parameters.

    Table 7-15 Parameters for creating a VM file system

    Parameter	Description	Value
    block_id=?	ID of the block device.	To obtain the value, run the show virtual_machine block owner_container_id=? command.
    container_id=?	ID of the VM container.	To obtain the value, run the show vm_container general command without parameters.

    Example:

    developer:/>create vm_fs general block_id=2 container_id=1 
    Command executed successfully.

11. Open the CLI and run the show vm_fs general command to check whether the VM file system has been created successfully.