No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Administrator Guide

OceanStor V3 Series V300R006

This document is applicable to OceanStor 2200 V3, 2600 V3, 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, 18500 V3, and 18800 V3. Routine maintenance activities are the most common activities for the storage device, including powering on or off the storage device, managing users, modifying basic parameters of the storage device, and managing hardware components. This document is intended for the system administrators who are responsible for carrying out routine maintenance activities, monitoring the storage device, and rectifying common device faults.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Expanding LUN Capacity

Expanding LUN Capacity

The following operations must be performed in sequence to expand the LUN capacity:

  1. Expand the LUN capacity on the storage system. Huawei provides technical support for this operation.
  2. Adjust the partition table, volume management, database, and application on the host. The customer takes responsibility for this operation. This document provides related expansion operations, which are for reference only.

Expansion on the host involves non-Huawei software. Huawei does not have any information about such software and therefore cannot help the customer to assess potential risks. According to Huawei's project experience, it is risky to expand LUN capacity due to the complex operations. Instead, it is a good practice to expand capacity by adding LUNs.

Known potential risks in expanding LUN capacity include but are not limited to:

  • Expanding LUN capacity on a host (expanding the volume and file system capacity of the host) poses risks to service continuity and data integrity, and the risks exist for all storage vendors, not just for Huawei.
  • Each operating system, file system, or volume management software has specific limits on LUN capacity. If the LUN capacity exceeds the limit after expansion, the LUN may fail to be identified by the host operating system or software. Moreover, the LUN cannot be downsized or restored after it is expanded. Consequently, the host may fail to access data, resulting in data loss.
NOTE:

For details about the maximum LUN capacity supported by each operating system, refer to the official documents of the operating system.

  • For partition tables, LUN capacity expansion may damage the partition tables or result in data loss.
  • For the volume management software, LUN capacity expansion may cause the disk space to exceed the capacity limit of the volume management software, resulting in an expansion failure.
  • For databases, LUN capacity expansion may disorder metadata, leading to data inconsistency or loss.
  • The impact of LUN capacity expansion cannot be determined when various applications are used in complex scenarios.

Understanding the Expansion Process

Understanding the expansion procedure helps ensure a smooth expansion.

Figure 5-52 shows the flowchart for expanding LUN capacity.

Figure 5-52 Expanding LUN capacity

Table 5-44 describes each step in detail.

Table 5-44 Steps for expanding LUN capacity

Procedure

Description

Perform a pre-expansion check.

Before expanding LUN capacity, make sure that the storage system meets expansion requirements. Obtain and record necessary information including the IP address of the application server that uses the LUN, the WWN of the LUN, or the host LUN ID.

Locate the LUN to be expanded.

Before expanding LUN capacity, confirm information about the LUN that carries service data to ensure a successful expansion.

Expand LUN capacity on the storage system.

Expand the LUN online to the required capacity.

Expand storage space for the application server.

After the expansion, scan for disks on the application server to detect and use the expanded LUN.

Performing a Pre-expansion Check

Storage space can be expanded without service interruption. Before the expansion, check the storage system environment and service environment to ensure a smooth expansion.

Prerequisites
  • You can log in to DeviceManager as the super administrator. Only a super administrator has expansion permission.
  • The storage system is running correctly.
  • You have obtained and recorded the WWN or IQN of the application server that uses the LUN and the WWN or LUN ID of the LUN. The LUN is correctly mapped to the application server and the host configuration on the storage system is correct.
Procedure
  1. Log in to DeviceManager as the super administrator. Make sure that the storage environment meets the expansion requirement.

    1. In the Basic Information area on the home page, check the device status and total capacity. Ensure that the storage system runs properly and has sufficient storage space.

      If the device status is Fault, contact Huawei technical engineers to locate and troubleshoot the problem. Start the expansion after the fault is rectified.

    2. In the Alarms area, check current alarm information. Click Show All.

      The Alarms and Events page is displayed, listing all current alarms.

      If there are alarms related to the disk domain, storage pool, or LUN to be expanded, follow instructions in the Suggestion to handle the alarms. These alarms include Storage Pool Is Degraded, Disk Domain Is Faulty, and LUN Is Faulty.

  2. On DeviceManager, confirm and record the host corresponding to the application server, the LUN to be expanded, and the LUN's owning storage pool.

    1. On the navigation bar of DeviceManager, click Provisioning.

      The Provisioning page is displayed.

    2. Click Host.

      The Host page is displayed.

    3. Based on the WWN or IQN of the application server you have recorded, find the host corresponding to the application server.
    4. Select the host and check whether its status is normal.

      If any alarm is found, clear it according to the handling suggestion.

    5. In the Mapped LUNs area, find the LUN to be expanded based on the LUN WWN or host LUN ID you have recorded. Record the LUN's capacity and owning storage pool.
    NOTE:

    If the LUN WWN or host LUN ID is not displayed in the Mapped LUNs area, click and choose WWN or Host LUN ID from the drop-down list. The LUN WWN or host LUN ID is displayed.

Locating the LUN to Be Expanded

Before expanding LUN capacity, confirm information about the LUN that carries service data to ensure a successful expansion.

Prerequisites
  • If a Fibre Channel network is used, the WWN of the Fibre Channel initiator has been obtained.
  • If an iSCSI network is used, the IQN of the iSCSI initiator has been obtained.
  • The UltraPath software has been installed on the host.
Context

For an HP-UX operating system, run scsimgr -p get_attr all_lun -a device_file -a wwid to view the WWNs of disks on the host.

Procedure
  1. On the storage system, obtain the WWN of the LUN mapped to the host.

    1. Log in to the command-line interface (CLI) of the storage system as a super administrator.
    2. Run show initiator initiator_type=? [ wwn=? | iscsi_iqn_name=? ] to query the host corresponding to the WWN or iSCSI IQN.

      Parameter

      Description

      Value

      initiator_type=?

      Type of an initiator.

      Possible values are:

      • iSCSI: iSCSI initiator.
      • FC: Fibre Channel initiator.

      wwn=?

      WWN of a Fibre Channel initiator. This parameter can be set only when initiator_type=? is FC.

      To obtain the value, run the show initiator command without parameters.

      iscsi_iqn_name=?

      IQN of an iSCSI initiator. This parameter can be set only when initiator_type=? is iSCSI.

      To obtain the value, run the show initiator command without parameters.

      admin:/>show initiator initiator_type=FC wwn=100000109b1c80ba
      
        WWN               : 100000109b1c80ba
        Running Status    : Online
        Free              : No
        Alias             : --
        Host ID           : 0
        Multipath Type    : Default
        Failover Mode     : --
        Path Type         : --
        Special Mode Type : --

      Host ID is the ID of the host corresponding to the WWN.

    3. Run show host lun host_id=? to view all LUNs mapped to the host.

      host_id=? represents the ID of the host.

      admin:/>show host lun host_id=2
      
        LUN ID  LUN Name    Host LUN ID
        ------  ----------  -----------
        74      LUN0750000  1
        75      LUN0750001  2
        76      LUN0750002  3

      LUN ID is the ID of each LUN mapped to the host from the storage system.

    4. Run the show lun general lun_id=? command to view the WWN of the LUN mapped to the host.

  2. On the host, view the WWN of the LUN.

    1. Log in to the CLI of UltraPath on the host.
    2. Run show vlun to query the WWNs of the disks on the host.
    NOTE:

    For details about how to use the show vlun command, see the UltraPath User Guide for specific operating systems.

  3. Compare the WWNs obtained in step 1 and step 2. If they are the same, the LUN is the one to be expanded.

    NOTE:

    For details about the preceding commands, see the Command Reference.

Expanding a LUN on the Storage System

A user granted the super administrator permission can use the OceanStor DeviceManager to expand LUN capacity and make expanded LUNs available to application servers.

Prerequisites
  • The storage system is working properly.
  • The capacity that you want to add to LUNs has been determined.
  • For V300R006C00/C10 storage systems, a LUN for which Snapshot, Clone, LUN Copy, HyperMirror, or SmartMigration is configured cannot be expanded.
  • For V300R006C20 and later version storage systems, a LUN for which Clone, LUN Copy, HyperMirror, or SmartMigration is configured cannot be expanded.
Context
  • For details about how to expand the capacity of remote replication LUNs, see "Expanding Remote Replication LUNs" in the Remote Replication Feature Guide specific to your product model.
  • For details about how to expand the capacity of HyperMetro LUNs, see "Expanding the Capacity of a HyperMetro LUN" in the BC&DR Solution Product Documentation (Active-Active DCs).
Procedure
  1. In the navigation tree on the right, choose Provisioning > LUN.

    NOTE:
    The operation path varies with user types in vStore scenarios:
    • System user: Click vStore, select the desired vStore, and click Details to go to the vStore view. Choose Provisioning > LUN.
    • vStore user: In the vStore view, choose Provisioning > LUN.

  2. Expand a LUN.

    1. In the LUN area, select the LUN that you want to expand and click Expand.
    2. In the Added Capacity area, enter the value of the capacity that you want to expand and select the unit.
    3. Click OK. The Info dialog box is displayed. Click OK.

  3. Verify and use the capacity added to the LUN.

    1. Under Block Storage Service on the Provisioning page, click LUN.

      The LUN page is displayed.

    2. Select the expanded LUN and check Capacity.

      If the displayed capacity is consistent with the actual capacity, the LUN is correctly expanded. If the LUN is incorrectly expanded, troubleshoot faults based on alarm information.

    3. After expanding the LUN, log in to the application server as a system administrator and scan for disks. The expanded LUN is available to the application server after being detected.

Expanding Storage Space for the Application Server

This operation enables you to configure the application server so that it can identify and use the expanded storage space after the capacity on a LUN is expanded.

Expanding LUN Capacity on a Windows Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running Windows Server 2008 as an example. For application servers running other versions of Windows operating systems, adjust the operations based on actual conditions.

Prerequisites

LUN capacity has been expanded on the storage system.

Context

In this example, the LUN is mapped as disk 3 on the application server. Its drive letter is G:\ and its capacity is expanded from 25 GB to 50 GB.

Procedure
  1. Log in to the Windows application server as an administrator.
  2. On the desktop, click Start and choose Administrative Tools > Server Manager.

    The Server Manager dialog box is displayed.

  3. In the left navigation tree of the Server Manager dialog box, right-click Disk Management and choose Rescan Disks from the shortcut menu.

    Figure 5-53 shows the scanning result. The unallocated space is displayed on the right side of disk G.

    Figure 5-53 Disk scanning result

  4. Right-click disk G and choose Extend Volume... from the shortcut menu.

    The Extend Volume Wizard dialog box is displayed, as shown in Figure 5-54.

    Figure 5-54 Extend Volume Wizard

  5. Click Next.

    The Select Disks page is displayed, as shown in Figure 5-55.

    Figure 5-55 Select Disks

    NOTE:
    • Disk 3 is the expanded LUN mapped to the application server.
    • You can specify the required space in Select the amount of space in MB. The default value is the maximum available space.

  6. Click Next.
  7. Click Finish.

    The Server Manager dialog box is displayed. Capacity expansion on the application server is complete.

Result

In the Server Manager dialog box, check the capacity of disk G after expansion, as shown in Figure 5-56.

Figure 5-56 Operation result

Expanding LUN Capacity on a SUSE Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running SUSE 11.0 as an example. For application servers running other versions of SUSE operating systems, adjust the operations based on actual conditions.

Prerequisites

LUN capacity has been expanded on the storage system.

Context

In this example, the LUN capacity is expanded from 25 GB to 50 GB. The drive letter of the mapped disk on the application server is sdf.

Procedure
  1. Scan for disks on the SUSE application server.

    1. Scan for disks.
      • If UltraPath is installed, run the hot_add command.
      • If UltraPath is not installed, perform the following operations:
        1. Run lsscsi to obtain the ID of the host that uses the LUN. The following is an example.
          SUSE:~ # lsscsi  [5:0:0:0]    disk    HUAWEI XXXX           2101  /dev/sdf

          In the preceding command output, 5 in [5:0:0:0] indicates the host ID, XXXX indicates a specific product model or brand.

        2. Run the echo '- - -' > /sys/class/scsi_host/hostN/scan command, where N indicates the host ID obtained in the preceding step.

          After the scanning is complete, the disk capacity remains 25 GB.

    2. Run echo 1 > /sys/block/sdf/device/rescan to rescan for disks.

      After the scanning is complete, the disk capacity becomes 50 GB.

    NOTE:

    sdf is the drive letter of the disk mapped from the LUN to the application server. The actual drive letter may be different.

  2. Run fdisk -l to query information about all disks on the application server.

    SUSE:~ # fdisk -l 
    Disk /dev/sdb: 598.0 GB, 597998698496 bytes 
    255 heads, 63 sectors/track, 72702 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Disk identifier: 0xc433d0ae 
     
     Device Boot      Start         End      Blocks Id  System 
    /dev/sdb1 *           1           9       72275+  83  Linux 
    /dev/sdb2              10         271     2104514+  83  Linux 
    /dev/sdb3             272       72703 581806279 83  Linux 
    /dev/sdb4               1           1           0+  ee  GPT 
     
    Partition table entries are not in disk order 
     
    Disk /dev/sdf: 53.7 GB, 53687091200 bytes 
    64 heads, 32 sectors/track, 51200 cylinders 
    Units = cylinders of 2048 * 512 = 1048576 bytes 
    Disk identifier: 0x00000000 
     
    Disk /dev/sdf doesn't contain a valid partition table     

  3. Run resize2fs /dev/sdf to add the new storage space to the file system of the LUN.

    • If the following command output is displayed, the file system is successfully expanded.
      SUSE:~ # resize2fs /dev/sdf 
      resize2fs 1.41.9 (22-Aug-2009) 
      Resizing the filesystem on /dev/sdf to 13107200 (4k) blocks. 
      The filesystem on /dev/sdf is now 13107200 blocks long.     
    • If the following information is displayed, run the e2fsck -f /dev/sdf command and then the resize2fs /dev/sdf command.
      SUSE:~ # resize2fs /dev/sdf 
      resize2fs 1.41.9 (22-Aug-2009) 
      Please run 'e2fsck -f /dev/sdf' first.

Using LVM to Expand LUN Capacity in SUSE

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses SUSE 11.0 as an example to describe how to non-disruptively expand the storage space on an application server using logical volume manager (LVM). For application servers running other versions of SUSE operating systems, adjust the operations based on actual conditions.

Prerequisites
  • LUN capacity has been expanded on the storage system.
  • A physical volume to be expanded has been determined.
Context

In this example, sdb5 is a physical volume under the drive letter of the disk mapped from the LUN to the application server. The capacity of sdb5 is expanded from 104 MB to 120 MB.

Procedure
  1. On the application server, check the block device ID of the LUN in the operating system.

    1. Run the hot_add command to scan for disks.
    2. Run the show vlun command to query the LUN WWN.
      UltraPath CLI #0 >show vlun 
      ------------------------------------------------------------------------------------------------------------------------------------ 
       Vlun ID      Disk            Name                    Lun WWN               Status Capacity Ctrl(Own/Work)  Array Name  Dev Lun ID 
          0         sda       WMQ_LUN_TEST_002  60022a11000beb2a0421c1cc000002d0  Normal  3.00GB        0B/0B      Array8.1       -- 
          1tagei         sdb       WMQ_LUN_TEST_003  60022a11000beb2a0421c2a2000002d1  Normal  3.00GB        0A/0A      Array8.1       -- 
          2         sdc       WMQ_LUN_TEST_004  60022a11000beb2a0421c365000002d2  Normal  3.00GB        0B/0B      Array8.1       -- 
          3         sdd       WMQ_LUN_TEST_005  60022a11000beb2a0421c4bd000002d3  Normal  3.00GB        0A/0A      Array8.1       -- 
      ------------------------------------------------------------------------------------------------------------------------------------        

      Lun WWN is the WWN of the LUN and Disk is the drive letter of the disk mapped from the LUN to the application server.

  2. Run the echo 1 > /sys/block/sdb5/device/rescan command to rescan for disks.

    NOTE:

    sdb5 is a physical volume under the drive letter of the disk mapped from the LUN to the application server. Change it to the actual physical volume in your operation.

  3. Run the pvresize /dev/sdb5 command to expand the physical volume.
  4. Run the lvextend -L +16M /dev/testvg/testlv command to expand the logical volume.

    lvextend  -L +16M /dev/testvg/testlv 
      Extending logical volume testlv to 120.00 MB 
      Logical volume testlv successfully resized     

    testlv is the logical volume to be expanded.

  5. Run the resize2fs /dev/testvg/testlv command to expand the file system.

    resize2fs /dev/testvg/testlv  
      resize2fs 1.41.9 (22-Aug-2009) 
      Resizing the filesystem on /dev/testvg/testlv to 122800 (1k) blocks. 
      The filesystem on /dev/testvg/testlv is now 122800 blocks long.     

Expanding LUN Capacity on a Red Hat Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running Red Hat 6.4 as an example. For application servers running other versions of Red Hat operating systems, adjust the operations based on actual conditions.

Prerequisites

LUN capacity has been expanded on the storage system.

Context

In this example, the LUN capacity is expanded from 25 GB to 50 GB. The drive letter of the mapped disk on the application server is sdh.

Procedure
  1. Scan for disks on the Red Hat application server.

    1. Scan for disks.
      • If UltraPath is installed, run the hot_add command.
      • If UltraPath is not installed, perform the following operations:
        1. Run the lsscsi command to obtain the ID of the host that uses the LUN. The following is an example.
          [root@localhost ~]# lsscsi  [5:0:0:0]    disk    HUAWEI XXXX           2101  /dev/sdh

          In the preceding command output, 5 in [5:0:0:0] indicates the host ID, XXXX indicates a specific product model or brand.

        2. Run the echo '- - -' > /sys/class/scsi_host/hostN/scan command, where N indicates the host ID obtained in the preceding step.

          After the scanning is complete, the disk capacity remains 25 GB.

    2. Run the echo 1 > /sys/block/sdh/device/rescan command to rescan for disks.

      After the scanning is complete, the disk capacity becomes 50 GB.

    NOTE:

    sdf is the drive letter of the disk mapped from the LUN to the application server. The actual drive letter may be different.

  2. Run fdisk -l to query information about all disks on the application server.

    [root@localhost ~]# fdisk -l 
     
    Disk /dev/sdb: 16.1 GB, 16106127360 bytes 
    64 heads, 32 sectors/track, 15360 cylinders 
    Units = cylinders of 2048 * 512 = 1048576 bytes 
    Sector size (logical/physical): 512 bytes / 512 bytes 
    I/O size (minimum/optimal): 512 bytes / 512 bytes 
    Disk identifier: 0x00000000 
     
     
    Disk /dev/sde: 107.4 GB, 107374182400 bytes 
    255 heads, 63 sectors/track, 13054 cylinders 
    Units = cylinders of 16065 * 512 = 8225280 bytes 
    Sector size (logical/physical): 512 bytes / 512 bytes 
    I/O size (minimum/optimal): 512 bytes / 512 bytes 
    Disk identifier: 0x00000000 
     
     
    Disk /dev/sdh: 53.7 GB, 53687091200 bytes 
    64 heads, 32 sectors/track, 51200 cylinders 
    Units = cylinders of 2048 * 512 = 1048576 bytes 
    Sector size (logical/physical): 512 bytes / 512 bytes 
    I/O size (minimum/optimal): 512 bytes / 512 bytes 
    Disk identifier: 0x00000000     

  3. Run resize2fs /dev/sdh to add the new storage space to the file system of the LUN.

    [root@localhost ~]# resize2fs /dev/sdh 
    resize2fs 1.41.12 (17-May-2010) 
    Filesystem at /dev/sdh is mounted on /fs1; on-line resizing required 
    old desc_blocks = 2, new_desc_blocks = 4 
    Performing an on-line resize of /dev/sdh to 13107200 (4k) blocks. 
    The filesystem on /dev/sdh is now 13107200 blocks long.

Expanding LUN Capacity on a Solaris Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running Solaris 10 as an example. For application servers running other versions of Solaris operating systems, adjust the operations based on actual conditions.

Prerequisites
  • LUN capacity has been expanded on the storage system.
  • Services on the LUN to be expanded have been stopped.
Context

This section uses the default disk-based UNIX File System (UFS) on a Solaris application server as an example to describe how to expand a LUN and its file system on a raw disk. The LUN will be expanded from 50 GB to 60 GB.

Procedure
  1. Run cfgadm -al to scan for the LUNs mapped to the application server.

    root@solaris:~# cfgadm -al 
    Ap_Id                          Type         Receptacle Occupant     Condition 
    c2                             scsi-sas     connected    configured unknown 
    c2::dsk/c2t6d0                 CD-ROM       connected    configured unknown 
    c4                             scsi-sas     connected    configured unknown 
    c4::w5000cca0258a82e5,0        disk-path    connected    configured unknown 
    c5                             scsi-sas     connected    unconfigured unknown 
    c6                             scsi-sas     connected    configured unknown 
    c6::w5000cca02570b521,0        disk-path    connected    configured unknown 
    c7                             scsi-sas     connected    unconfigured unknown 
    c10                            fc-private connected    configured unknown 
    c10::20080022a10bc14f          disk         connected    configured unknown 
    c11                            fc           connected    unconfigured unknown 
    usb0/1                         unknown      empty        unconfigured ok 
    usb0/2                         unknown      empty        unconfigured ok 
    usb0/3                         unknown      empty        unconfigured ok 
    usb1/1                         unknown      empty        unconfigured ok 
    usb1/2                         unknown      empty        unconfigured ok 
    usb2/1                         unknown      empty        unconfigured ok 
    usb2/2                         usb-hub      connected    configured ok 
    usb2/2.1                       unknown      empty        unconfigured ok 
    usb2/2.2                       unknown      empty        unconfigured ok 
    usb2/2.3                       usb-hub      connected    configured ok 
    usb2/2.3.1                     unknown      empty        unconfigured ok 
    usb2/2.3.2                     usb-storage  connected    configured ok 
    usb2/2.3.3                     usb-communi  connected    configured ok 
    usb2/2.4                       usb-device connected    configured ok 
    usb2/3                         unknown      empty        unconfigured ok 
    usb2/4                         usb-hub      connected    configured ok 
    usb2/4.1                       unknown      empty        unconfigured ok 
    usb2/4.2                       unknown      empty        unconfigured ok 
    usb2/4.3                       unknown      empty        unconfigured ok 
    usb2/4.4                       unknown      empty        unconfigured ok 
    usb2/5                         unknown      empty        unconfigured ok

  2. Run umount /mnt/ to unmount the disks corresponding to the LUN that you want to expand on the application server.

    /mnt/ indicates the mount directory of the disks corresponding to the LUN.

    NOTE:

    If disks of the LUN that you want to expand are not mounted, skip this operation.

  3. Run format to query the information about all disks detected by the application server.

    root@solaris:~# format 
    Searching for disks...done 
     
    AVAILABLE DISK SELECTIONS: 
           0. c0t5000CCA0258A82E4d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625>  solaris 
              /scsi_vhci/disk@g5000cca0258a82e4 
              /dev/chassis//SYS/HDD0/disk 
           1. c0t5000CCA02570B520d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625>  solaris 
              /scsi_vhci/disk@g5000cca02570b520 
              /dev/chassis//SYS/HDD4/disk 
           2. c10t5d0 <drive type unknown> 
              /pci@400/pci@2/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w20080022a10bc14f,0 
           3. c10t5d1 <HUAWEI-XXXXXX-2201 cyl 6398 alt 2 hd 64 sec 256> 
              /pci@400/pci@2/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w20080022a10bc14f,1 
    Specify disk (enter its number):

    In the preceding command output, c10t5d1 indicates the drive letter mapped by the LUN to the application server.

  4. Enter 3 after Specify disk (enter its number), which is the ID of c10t5d1.

    Specify disk (enter its number): 3 
    selecting c10t5d1 
    [disk formatted] 
    Note: detected additional allowable expansion storage space that can be  
    added to current SMI label's computed capacity. 
    Select <partition> <expand> to adjust the label capacity. 
     
    FORMAT MENU: 
            disk       - select a disk 
            type       - select (define) a disk type 
            partition  - select (define) a partition table 
            current    - describe the current disk 
            format     - format and analyze the disk 
            repair     - repair a defective sector 
            label      - write label to the disk 
            analyze    - surface analysis 
            defect     - defect list management 
            backup     - search for backup labels 
            verify     - read and display labels 
          save       - save new disk/partition definitions 
            inquiry    - show disk ID 
            volname    - set 8-character volume name 
            !<cmd>     - execute <cmd>, then return 
            quit 
    format>

  5. Run type to view the disk type.

    format> type 
     
    AVAILABLE DRIVE TYPES: 
            0. Auto configure 
            1. Quantum ProDrive 80S 
            2. Quantum ProDrive 105S 
            3. CDC Wren IV 94171-344 
            4. SUN0104 
            5. SUN0207 
            6. SUN0327 
            7. SUN0340 
            8. SUN0424 
            9. SUN0535 
            10. SUN0669 
            11. SUN1.0G 
            12. SUN1.05 
            13. SUN1.3G 
            14. SUN2.1G 
            15. SUN2.9G 
            16. Zip 100 
            17. Zip 250 
            18. Peerless 10GB 
            19. SUN300G 
            20. HUAWEI-XXXXXX-2201 
            21. other 
    Specify disk type (enter its number)[20]:

  6. After Specify disk type (enter its number)[20]:, enter 0 to automatically update disks, re-define the disk type, and refresh the disk capacity.

    Specify disk type (enter its number)[20]: 0 
    c10t5d1: configured with capacity of 59.98GB 
    <HUAWEI-XXXXXX-2201 cyl 7678 alt 2 hd 64 sec 256> 
    selecting c10t5d1 
    [disk formatted]

    After the operations are complete, the disk capacity becomes 60 GB.

  7. Run partition and then run print to view disk partitions.

    format> partition 
     
    PARTITION MENU: 
            0      - change `0' partition 
            1      - change `1' partition 
            2      - change `2' partition 
            3      - change `3' partition 
            4      - change `4' partition 
            5      - change `5' partition 
            6      - change `6' partition 
            7      - change `7' partition 
            select - select a predefined table 
            modify - modify a predefined partition table 
            name - name the current table 
            print  - display the current table 
            label  - write partition map and label to the disk 
            !<cmd> - execute <cmd>, then return 
            quit 
    partition> print 
    Current partition table (default): 
    Total disk cylinders available: 7678 + 2 (reserved cylinders) 
     
    Part      Tag    Flag     Cylinders        Size            Blocks 
      0       root    wm       0 - 15      128.00MB    (16/0/0)      262144 
      1       swap    wu      16 - 31      128.00MB    (16/0/0)      262144 
      2     backup    wu       0 - 7677       59.98GB    (7678/0/0) 125796352 
      3 unassigned    wm       0               0         (0/0/0)            0 
      4 unassigned    wm       0               0         (0/0/0)            0 
      5 unassigned    wm       0               0         (0/0/0)            0 
      6        usr    wm      32 - 7677       59.73GB    (7646/0/0) 125272064 
      7 unassigned    wm       0               0         (0/0/0)            0     
    NOTE:

    Generally, if Part of a partition is numbered 2, the partition indicates the entire disk that mapped to the application server.

  8. Run l and enter y to label the LUN that has been expanded.

    partition> l 
    Ready to label disk, continue? y     

  9. Run mount /dev/dsk/c10t5d1s6 /mnt/ to mount the disk.
  10. Run growfs -M /mnt /dev/rdsk/c10t5d1s6 to expand the file system of the LUN.

    root@solaris:~# growfs -M /mnt /dev/rdsk/c10t5d1s6 
    /dev/rdsk/c10t5d1s6:    125272064 sectors in 20390 cylinders of 48 tracks, 128 sectors 
            61168.0MB in 1275 cyl groups (16 c/g, 48.00MB/g, 5824 i/g) 
    super-block backups (for fsck -F ufs -o b=#) at: 
     32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920, 
    Initializing cylinder groups: 
    ......................... 
    super-block backups for last 10 cylinder groups at: 
     124360864, 124459296, 124557728, 124656160, 124754592, 124853024, 124951456, 
     125049888, 125148320, 125246752

  11. Run df -k to view the file system capacity.

    root@solaris:~# df -k 
    Filesystem           1024-blocks        Used Available Capacity  Mounted on 
    rpool/ROOT/solaris     103219200     2269688    79378520     3%    / 
    /devices                       0           0           0     0%    /devices 
    /dev                           0           0           0     0%    /dev 
    ctfs                           0           0           0     0%    /system/contract 
    proc                           0           0           0     0%    /proc 
    mnttab                         0           0           0     0%    /etc/mnttab 
    swap                    30640088        2272    30637816     1%    /system/volatile 
    objfs                        0           0           0     0%    /system/object 
    sharefs                        0           0           0     0%    /etc/dfs/sharetab 
    fd                             0           0           0     0%    /dev/fd 
    rpool/ROOT/solaris/var 
                           103219200      200868    79378520     1%    /var 
    swap                    30637816           0    30637816     0%    /tmp 
    rpool/VARSHARE         103219200          48    79378520     1%    /var/share 
    rpool/export           103219200          32    79378520     1%    /export 
    rpool/export/home      103219200          31    79378520     1%    /export/home 
    rpool                  103219200          73    79378520     1%    /rpool 
    /dev/dsk/c2t6d0s2         694700      694700           0 100%    /media/Oracle_Solaris-11_1-Text-SPARC 
    /dev/dsk/c10t5d1s6      61687396       61185    61120192     1%    /mnt

Expanding LUN Capacity on an AIX Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running AIX 6.1 as an example. For application servers running other versions of AIX operating systems, adjust the operations based on actual conditions.

Prerequisites
  • LUN capacity has been expanded on the storage system.
  • Services on the LUN to be expanded have been stopped.
Context

In the following example, the LUN to be expanded is LUN005 and its capacity is 25 GB. The capacity of the file system created on the LUN is 24 GB. The LUN and file system will be expanded to 50 GB and 48 GB respectively. The volume group name and logical volume name of the LUN to be expanded are vg1 and lv1 respectively. The mount directory of the file system that uses the LUN is /mnt/lv1.

Procedure
  1. Scan for disks on the AIX application server.

    • If the LUN that you want to expand has been mapped to the application server and has mapping relationship with the application server during the expansion process, run rmdev -dl diskName to delete disk information before performing the follow-up operations. In the command, diskName indicates the disk corresponding to the LUN before expansion.
    • If the mapping between the LUN and application server is canceled before expansion and rebuilt after expansion, directly perform the following operations.

    Run cfgmgr -v to scan for the LUN.

    After the LUN is scanned, AIX automatically identifies the LUN that is mapped to the application server as a drive letter in hdisk format.

  2. Run the lsdev -Cc disk command to view the information about the disks that have been detected.

    # lsdev -Cc disk 
    hdisk0  Available 01-08-00 SAS Disk Drive 
    hdisk1  Available 01-08-00 SAS Disk Drive 
    hdisk2  Available 04-00-02 MPIO Other FC SCSI Disk Drive 
    hdisk3  Available 04-00-02 MPIO Other FC SCSI Disk Drive 
    hdisk4  Available 03-01-02 Other FC SCSI Disk Drive 
    hdisk5  Available 04-01-02 HUAWEI XXXX FC Disk Drive

    In the command output, XXXX indicates a specific product model or brand.

  3. Run upadm show lun to check the drive letter of the LUN that you want to expand.

    # upadm show lun 
    Vendor of /dev/hdisk0 is not HUAWEI, XXXX, XXXX or XXXX 
    Vendor of /dev/hdisk1 is not HUAWEI, XXXX, XXXX or XXXX 
    Vendor of /dev/hdisk2 is not HUAWEI, XXXX, XXXX or XXXX 
    Vendor of /dev/hdisk3 is not HUAWEI, XXXX, XXXX or XXXX 
    ----------------------------------------------------------------------------------------------- 
    Device Name: Lun Name: Vendor ID:  Type:    Serial Number:  Device WWN:            
    ----------------------------------------------------------------------------------------------- 
    /dev/hdisk5 LUN005       HUAWEI     XXXX 1T50214955      60022a1100098e6703da136f0000000a

    If there are multiple disks, the command output lists the drive letter of each disk. At the bottom of the command output, the drive letter of the newly created LUN is displayed. In this example, the LUN name is LUN005 and its drive letter is hdisk5. In the command output, XXXX indicates a specific product model or brand.

  4. Run umount /mnt/lv1 to unmount the file system.

    In the command, /mnt/lv1 indicates the mount directory of the file system.

  5. Run varyoffvg vg1 to deactivate volume group vg1.

    In the command, vg1 indicates the name of the volume group corresponding to the LUN that you want to expand.

  6. Run bootinfo -s hdiskX to check the LUN capacity after expansion. In the command, X indicates the number of the drive letter. In this example, X is 5.

     
    # bootinfo -s hdisk5 
    51200

    In the preceding command output, the unit is MB, and the capacity is 51,200 MB (50 GB), which is the same as the expansion result displayed on the storage system.

  7. Run varyonvg vg1 to activate volume group vg1.
  8. Refresh the capacity of the volume group corresponding to the LUN.

    1. Run chvg -g vg1 to refresh the volume group.
      # chvg -g vg1 
      0516-1164 chvg: Volume group vg1 changed.  With given characteristics vg1 
              can include up to 64 physical volumes with 2032 physical partitions each.
    2. Run lsvg vg1 and check the volume group parameters.
      # lsvg vg1 
      VOLUME GROUP:       vg1                 VG IDENTIFIER:  00f6e07400004c00000000011660e3d1 
      VG STATE:           active              PP SIZE:        32 megabyte(s) 
      VG PERMISSION:      read/write          TOTAL PPs:      1599 (51168 megabytes) 
      MAX LVs:            512                 FREE PPs:       62 (1984 megabytes) 
      LVs:                2                   USED PPs:       1537 (49184 megabytes) 
      OPEN LVs:           0                   QUORUM:         2 (Enabled) 
      TOTAL PVs:          1                   VG DESCRIPTORS: 2 
      STALE PVs:          0                   STALE PPs:      0 
      ACTIVE PVs:         1                   AUTO ON:        yes 
      MAX PPs per VG:     130048                                 
      MAX PPs per PV:     2032                MAX PVs:        64 
      LTG size (Dynamic): 256 kilobyte(s)     AUTO SYNC:      no 
      HOT SPARE:          no                  BB POLICY:      relocatable 

      In the command output, pay attention to the PP SIZE parameter, which is relevant to the logical volume size when you create or modify a logical volume. In this example, the value of PP SIZE is 32 MB.

  9. Modify the capacity of the logical volume to meet the needs of the file system.

    1. Run lslv lv1 and check the logical volume parameters.
      # lslv lv1 
      LOGICAL VOLUME:     lv1                    VOLUME GROUP: vg1 
      LV IDENTIFIER:      00f6e07400004c00000000011660e3d1.1 PERMISSION:     read/write 
      VG STATE:           active/complete        LV STATE:       closed/syncd 
      TYPE:               jfs2                   WRITE VERIFY: off 
      MAX LPs:            768                    PP SIZE:        32 megabyte(s) 
      COPIES:             1                      SCHED POLICY: parallel 
      LPs:                768                    PPs:            768 
      STALE PPs:          0                      BB POLICY:      relocatable 
      INTER-POLICY:       minimum                RELOCATABLE:    yes 
      INTRA-POLICY:       middle                 UPPER BOUND:    128 
      MOUNT POINT:        /mnt/lv1               LABEL:          /mnt/lv1 
      MIRROR WRITE CONSISTENCY: on/ACTIVE                               
      EACH LP COPY ON A SEPARATE PV ?: yes                                     
      Serialize IO ?:     NO                       

      lv1 indicates the name of a logical volume in the volume group. Pay attention to the MAX LPs, LPs, and PP SIZE parameters in the command output, which indicate the maximum number of logical partitions, number of logical partitions, and size of the physical partition, respectively. The value of MAX LPs multiplied by PP SIZE is the size of the logical volume, and the value of LPs multiplied by PP SIZE is the capacity of the logical volume's file system. In this example, the values of MAX LPs and LPs are both 768, and the value of PP SIZE is 32 MB. Therefore, the capacities of the logical volume and the file system are both 24,576 MB (24 GB).

    2. Run smit lv.
      # smit lv 
                                      Logical Volumes 
       
      Move cursor to desired item and press Enter. 
       
        List All Logical Volumes by Volume Group 
        Add a Logical Volume 
        Set Characteristic of a Logical Volume 
        Show Characteristics of a Logical Volume 
        Remove a Logical Volume 
        Copy a Logical Volume 
       
       
      F1=Help             F2=Refresh          F3=Cancel           Esc+8=Image 
      Esc+9=Shell         Esc+0=Exit          Enter=Do                    
    3. In the command output, select Set Characteristic of a Logical Volume and press Enter.
                           Set Characteristic of a Logical Volume 
       
      Move cursor to desired item and press Enter. 
       
        Change a Logical Volume 
        Rename a Logical Volume 
        Increase the Size of a Logical Volume 
        Add a Copy to a Logical Volume 
        Remove a Copy from a Logical Volume
    4. In the command output, select Change a Logical Volume and press Enter.
                                  Change a Logical Volume 
       
      Type or select a value for the entry field. 
      Press Enter AFTER making all desired changes. 
       
                                                              [Entry Fields] 
      * LOGICAL VOLUME name                                []                      +
    5. Press Esc+4 to go to the logical volume name list. Select the logical volume you want to modify and press Enter.
                                  Change a Logical Volume 
       
      Type or select values in entry fields. 
      Press Enter AFTER making all desired changes. 
       
                                                            [Entry Fields] 
      * Logical volume NAME                                 lv1 
        Logical volume TYPE                                [jfs2]                  + 
        POSITION on physical volume                         middle                 + 
        RANGE of physical volumes                           minimum                + 
        MAXIMUM NUMBER of PHYSICAL VOLUMES                 [128]                    # 
          to use for allocation 
        Allocate each logical partition copy                yes                    + 
          on a SEPARATE physical volume? 
        RELOCATE the logical volume during                  yes                    + 
          reorganization? 
        Logical volume LABEL                               [/mnt/lv1] 
        MAXIMUM NUMBER of LOGICAL PARTITIONS               [1536]                   # 
        SCHEDULING POLICY for writing/reading               parallel               +  
          logical partition copies 
        PERMISSIONS                                         read/write             + 
        Enable BAD BLOCK relocation?                        yes                    + 
        Enable WRITE VERIFY?                                no                     + 
        Mirror Write Consistency?                           active                 + 
        Serialize IO?                                       no                     + 
        Mirror Pool for First Copy                                                 + 
        Mirror Pool for Second Copy                                                + 
        Mirror Pool for Third Copy                                                 +     
    6. In the command output, select the MAXIMUM NUMBER of LOGICAL PARTITIONS parameter (that is, the MAX LPs parameter) and enter the maximum number of logical partitions for the logical volume.

      Because a file system is created on a logical volume, you must expand the capacity of the logical volume before the file system can be expanded. The capacity of the logical volume must not be smaller than that of the file system. Otherwise, the file system will fail to be expanded. In this example, the capacity of the file system will be expanded to 48 GB. First, you must adjust the maximum number of logical partitions to ensure that the capacity of the logical volume is greater than or equal to 48 GB (49,152 MB). To achieve this, the maximum number of logical partitions must not be smaller than 1536 (49,152 MB/32 MB).

    7. After modifying the parameter, press Enter.
                     COMMAND STATUS 
       
      Command: OK            stdout: no            stderr: no 
       
      Before command completion, additional instructions may appear below.     
    8. Press Esc+0 to exit the logical volume configuration interface.

  10. Expand the file system on the lv1 logical volume.

    1. Run chfs -a size=48G /mnt/lv1 to expand the file system.
      # chfs -a size=48G /mnt/lv1 
      Filesystem size changed to 100663296

      As shown in the command output, the capacity of the file system has been expanded to 48 GB.

    2. Run mount /mnt/lv1 to mount the file system again.

Expanding LUN Capacity on an HP-UX Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running HP-UX 11i v3 as an example. For application servers running other versions of HP-UX operating systems, adjust the operations based on actual conditions.

Prerequisites
  • LUN capacity has been expanded on the storage system.
  • Services on the LUN to be expanded have been stopped.
Context

In this example, the LUN capacity is expanded from 25 GB to 50 GB and the mount directory for the LUN is /test/.

Procedure
  1. Scan for LUNs on the HP-UX application server.

    1. Run ioscan to scan for hardware.
    2. Run ioscan -funNC disk to query information about detected LUNs.
    bash-3.2# ioscan -funNC disk 
    Class     I  H/W Path  Driver S/W State H/W Type     Description 
    =================================================================== 
    disk      2  64000/0xfa00/0x0 esdisk   CLAIMED     DEVICE       HP      DG146ABAB4 
                          /dev/disk/disk2      /dev/disk/disk2_p1 /dev/rdisk/disk2     /dev/rdisk/disk2_p1 
    disk      3  64000/0xfa00/0x1 esdisk CLAIMED     DEVICE       HP      DG146ABAB4 
                          /dev/disk/disk3      /dev/disk/disk3_p1 /dev/disk/disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/disk3     /dev/rdisk/disk3_p1  /dev/rdisk/disk3_p2  /dev/rdisk/disk3_p3 
    disk      5  64000/0xfa00/0x2 esdisk CLAIMED     DEVICE       TEAC    DV-28E-V 
                          /dev/disk/disk5 /dev/rdisk/disk5 
    disk    399  64000/0xfa00/0x90  esdisk CLAIMED     DEVICE       HUAWEI XXXXXX 
                          /dev/disk/disk399 /dev/rdisk/disk399

    In this example, /dev/disk/disk399 indicates the device file of the LUN mapped to the application server.

    NOTE:

    If the operating system is HP-UX 11i v2 or HP-UX 11i v1, run the ioscan -funC disk command to query LUNs detected by the application server.

  2. Run umount /test/ to unmount the file system of the LUN.

    /test/ indicates the mount directory of the file system.

  3. Run extendfs -F vxfs /dev/disk/disk399 to expand the file system of the LUN.

    vxfs indicates the file system type.

  4. Run mount /dev/disk/disk399 /test/ to mount the file system of the LUN.
  5. Run bdf to check the file system capacity after expansion.

    bash-3.2# bdf 
    Filesystem          kbytes    used avail %used Mounted on 
    /dev/vg00/lvol3    1048576  920416  127376 88% / 
    /dev/vg00/lvol1    1835008  368824 1454800 20% /stand 
    /dev/vg00/lvol8    8912896 2309816 6552824 26% /var 
    /dev/vg00/lvol7    6553600 3012368 3513640 46% /usr 
    /dev/vg00/lvol4     524288 23504  497008    5% /tmp 
    /dev/vg00/lvol6    7864320 4358216 3479048 56% /opt 
    /dev/vg00/lvol5     131072 64088 66464 49% /home 
    /dev/disk/disk399 52428800 79504 49077472    0% /test

    The preceding command output shows that the capacity of the file system becomes 50 GB.

Expanding LUN Capacity on a VMware ESX Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses an application server running VMware ESXi 6.5.0 as an example. For application servers running other versions of VMware ESX operating systems, adjust the operations based on actual conditions.

Prerequisites

LUN capacity has been expanded on the storage system.

Context

In this example, the LUN capacity is expanded from 25 GB to 50 GB. The ID of the LUN to be expanded is 3.

Procedure
  1. In vSphere Client, click the Configure tab.
  2. In the navigation tree on the left, click Storage > Storage Devices.
  3. On the Storage Devices page, view the device mapped from the LUN to be expanded on the application server, as shown in Figure 5-57.

    Figure 5-57 Device mapped from the LUN to be expanded on the application server

  4. On the Devices page, click All Actions > Rescan Storage.

    The Rescan Storage dialog box is displayed, as shown in Figure 5-58.

    Figure 5-58 Rescan Storage dialog box

  5. Click OK.

    It takes 2 to 4 minutes to scan for new storage devices and VMFS volumes. You can check the task status in the Recent Tasks area at the lower part of the main window.

    • If the task status is In Progress as shown in Figure 5-59, the scanning is ongoing.
      Figure 5-59 Scanning ongoing

    • If the task status is Completed as shown in Figure 5-60, the scanning is completed.
      Figure 5-60 Scanning completed

  6. Click Datastores.

    On the Datastores page, view the datastore mapped from the LUN to be expanded on the application server, as shown in Figure 5-61.

    Figure 5-61 Datastore mapped from the LUN to be expanded on the application server

  7. Right-click the datastore corresponding to the LUN to be expanded, and choose Increase Datastore Capacity from the shortcut menu.

    The Increase Datastore Capacity dialog box is displayed, as shown in Figure 5-62.

    Figure 5-62 Increase Datastore Capacity dialog box

  8. Select the datastore corresponding to the LUN to be expanded and click Next.
  9. Set Partition Configuration and Increase Size by. The maximum storage space is recommended, as shown in Figure 5-63. Click Next.

    Figure 5-63 Setting the datastore size

  10. Click Finish.
Result
  • On the Datastores page, view the expanded datastore, as shown in Figure 5-64.
Figure 5-64 Datastore mapped from the expanded LUN on the application server

  • On the Storage Devices page, view the expanded device, as shown in Figure 5-65.
Figure 5-65 Device mapped from the expanded LUN on the application server

Expanding LUN Capacity on a Hyper-V Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses a Windows Server 2016 Hyper-V cluster as an example. For Hyper-V clusters of other versions, adjust the operations based on actual conditions.

Prerequisites

LUN capacity has been expanded on the storage system.

Context

In this example, the Hyper-V cluster consists of two application servers: WIN2016_HOST1 and WIN2016_HOST2. The LUN to be expanded is mapped to disk 6 and disk 7 respectively on the two application servers. The LUN capacity is expanded from 25 GB to 58 GB.

Procedure
  1. Query the Owner Node of the shared volume of the cluster to be expanded.

    1. Log in to either of the Windows application servers in the Hyper-V cluster as an administrator.
    2. On the Windows desktop, click Start and choose Server Manager.

      The Server Manager dialog box is displayed.

    3. Choose Tools > Failover Cluster Manager.

      The Failover Cluster Manager dialog box is displayed.

    4. In the navigation tree on the left, choose Storage > Disks under the Hyper-V cluster to be expanded. In the Disks area, view the Owner Node of the shared volume of the cluster.

      In this example, the Owner Node of the shared volume of the cluster is WIN2016_HOST2.

  2. Perform volume capacity expansion on the Owner Node of the shared volume of the cluster to be expanded. The following procedure takes the WIN2016_HOST2 application server as an example.

    1. Log in to the WIN2016_HOST2 application server as an administrator.
    2. Go to the Server Manager page. Choose File and Storage Services > Volumes > Disks.
    3. Click TASKS > Rescan Storage to scan for disks on all application servers in the cluster.

      After the scanning is complete, check the capacity of the partitions to be expanded in the DISKS area. In this example, the total capacity of the partitions to be expanded is 58 GB, among which 33 GB is the unallocated capacity.

    4. On the Server Manager page, choose Tools > Computer Management.

      The Computer Management dialog box is displayed.

    5. Choose Storage > Disk Management in the navigation tree.

    6. Right-click Disk 7 and choose Extend Volume… from the shortcut menu.

      The Extend Volume Wizard dialog box is displayed.

    7. Click Next.

      The Select Disks page is displayed.

      NOTE:
      • Disk 7 is the disk mapped from the LUN to be expanded on the application server.
      • You can specify the required space in Select the amount of space in MB. The default value is the maximum available space.
    8. Click Next.
    9. Click Finish. Partition expansion on the application server is complete.
    NOTE:

    To expand the capacity of the shared volume of the cluster, you only need to perform partition expansion on the Owner Node. After this step is complete, perform Step 3 to scan for disks. Other application servers in the cluster can identify the partitions after capacity expansion.

  3. Scan the shared volume and check the result of capacity expansion.

    1. On the Server Manager page, choose TASK > Rescan Storage to scan disks of all application servers in the cluster.

      After the scanning is complete, check the capacity after expansion in the DISKS area. In this example, the total capacity after disk scanning is 58 GB.

    2. On the Failover Cluster Manager page, right-click the shared volume of the cluster and choose Properties from the shortcut menu.

      The Properties dialog box is displayed.

    3. If the volume status is Online and the total volume capacity is the expected capacity after expansion, the volume is successfully expanded.

  4. Expand the disk capacity of a Hyper-V VM. This section describes how to expand the test VM on the WIN2016_HOST2 application server.

    1. On the Server Manager page, choose Tools > Hyper-V Manager.

      The Hyper-V Manager dialog box is displayed.

    2. (Optional) Stop the VM. Right-click the VM to be expanded and choose Turn Off from the shortcut menu.
      NOTE:
      • For a VM that uses the IDE disk controller, you must stop the VM before performing capacity expansion.
      • For Windows Server 2012 R2 to Windows Server 2019, if the VM uses the SCSI disk controller, skip this step.
      • For operating systems earlier than Windows Server 2012 R2, if the VM uses the SCSI disk controller, you must stop the VM before capacity expansion.

    3. Right-click the VM name, and choose Settings from the shortcut menu.
      Figure 5-66 Settings dialog box

    4. In the navigation tree on the left, choose Hard Drive under the disk controller node to be expanded, and click Edit.
      Figure 5-67 Edit Virtual Hard Disk Wizard dialog box

    5. In the navigation tree on the left, click Choose Action, select Expand, and click Next.

      The Configure Disk page is displayed.

    6. Enter the capacity after expansion in the New size text box and click Finish. The disk capacity expansion for the Hyper-V VM is completed.
    7. If the VM is stopped, right-click the VM and choose Start from the shortcut menu to restart the VM.

Expanding LUN Capacity on a FusionCompute Application Server

After expanding LUN capacity on the storage system, configure the corresponding application server to identify and use the expanded storage space. This section uses FusionCompute 6.3.0 as an example. For FusionCompute application servers of other versions, adjust the operations based on actual conditions.

Prerequisites
  • LUN capacity has been expanded on the storage system.
  • No more than 64 capacity expansion operations have been performed on a datastore, and the total datastore capacity is not greater than 64 TB.
  • The datastore type is virtualized SAN storage.
Procedure
  1. Scan for storage devices.

    1. Log in to FusionCompute.
    2. Click Host and Cluster.

      The Host and Cluster page is displayed.

    3. In the navigation tree, choose site > Cluster > Host.
    4. In the middle function pane, choose Resource > Storage Device.

      The storage device list is displayed.

    5. Click Scan.

      The Information dialog box is displayed.

    6. Click OK. The system starts to scan for storage devices.
      NOTE:

      Click click here in the Information dialog box. On the Task Center page that is displayed, check the scan progress.

      After the scan is complete, you can view the capacity of IP SAN storage, which is the LUN mapped from the storage system to the application server.

  2. Expand the datastore capacity.

    1. In the middle function pane, choose Resource > Storage Device.
    2. Right-click the row of the datastore to be expanded and choose Add Capacity from the shortcut menu.

    3. The storage devices that can be added are displayed in the list.
    4. Select a storage device and click OK.

      The Information dialog box is displayed.

    5. Click OK.

Download
Updated: 2019-07-12

Document ID: EDOC1000138854

Views: 38565

Downloads: 2091

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next