Reallocating VM File System Capacity (Applicable to V500R007C73)

Prerequisites

A VM file system has been created.

Context

For V500R007C72, the storage system can automatically create VM file systems by using the Initialize VM Service function on DeviceManager. As a result, we can use this feature to reallocate VM file system capacity.

Procedure of Reallocating the VM File System Capacity

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

Procedure

1. Power off the VM.
   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 a VM exists in the VM file system, power off the VM first.
   • If the VM fails to be powered off, perform the step as instructed in Forcibly Powering Off a VM.
   • If no VM is created on the VM file system, skip this step.

2. Delete the VM.

   Ensure that the VM is powered off, the health status of the VM file system is normal, and the VM file system is mounted.

   Run the delete virtual_machine general vm_id=? command to delete the VM.

   • You can run the show virtual_machine general command to view the VM status.
   • You can run the show vm_fs general command to view the VM file system status.
   • For V500R007C72SPC100 and later versions, you can run the delete virtual_machine general vm_id=? is_force=? command to forcibly delete a VM.

3. 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-16 lists the corresponding parameters.

   Table 7-16 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.

4. 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-17 lists the corresponding parameters.

   Table 7-17 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.

5. Delete the mapping view.
   1. Choose Provisioning > Mapping View.
   2. Delete the mapping views vm_mv_reserved_container0 and vm_mv_reserved_container1 in sequence.

6. Delete the LUN group.
   1. Choose Provisioning > LUN > LUN Group.
   2. Delete LUN groups vm_lg_reserved_container0 and vm_lg_reserved_container1 in sequence.

7. Delete the LUN.
   1. Choose Provisioning > LUN.
   2. Delete LUNs vm_lun_reserved_container0 and vm_lun_reserved_container1 in sequence.

8. Delete the host group.
   1. Choose Provisioning > Host > Host Group.
   2. Delete host groups vm_hg_reserved_container0 and vm_hg_reserved_container1 in sequence.

9. Delete the host.
   1. Choose Provisioning > Host.
   2. Delete hosts vm_host_reserved_container0 and vm_host_reserved_container1 in sequence.

10. Choose VM > Initialize. Reallocate the file system capacity of a VM using the Initialize VM Service function on the GUI.

    For V500R007C73, see Initializing the VM Service.

    The system automatically initializes the storage resources related to the VM service, including:

    1. Create thick LUN vm_lun_reserved_container0 and set its owning controller to 0A.

       Create thick LUN vm_lun_reserved_container1 and set its owing controller to 0B.

    2. Create LUN groups vm_lg_reserved_container0 and vm_lg_reserved_container1.
    3. Add LUN vm_lun_reserved_container0 to LUN group vm_lg_reserved_container0.

       Add LUN vm_lun_reserved_container1 to LUN group vm_lg_reserved_container1.

    4. Create hosts vm_host_reserved_container0 and vm_host_reserved_container1.
    5. Add the vHBA initiator whose WWN starts with 2100 to host vm_host_reserved_container0.

       Add the vHBA initiator whose WWN starts with 2101 to host vm_host_reserved_container1.

    6. Create host groups vm_hg_reserved_container0 and vm_hg_reserved_container1.
    7. Add host vm_host_reserved_container0 to host group vm_hg_reserved_container0.

       Add host vm_host_reserved_container1 to host group vm_hg_reserved_container1.

    8. Create mapping views vm_mv_reserved_container0 and vm_mv_reserved_container1.
    9. Add host group vm_hg_reserved_container0 to mapping view vm_mv_reserved_container0.

       Add host group vm_hg_reserved_container1 to mapping view vm_mv_reserved_container1.

    10. Add LUN group vm_lg_reserved_container0 to mapping view vm_mv_reserved_container0.

        Add LUN group vm_lg_reserved_container1 to mapping view vm_mv_reserved_container1.

    11. Scan for VM block devices generated by LUNs.
    12. Create file systems used by the VM container.