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 15

OceanStor 5300 V3, 5500 V3, 5600 V3, 5800 V3, and 6800 V3 Storage System V300R003

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 applies to 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

If LUN space where service data resides is insufficient, you can increase LUN capacity to meet your service requirements.

The following operations must be performed in sequence to expand the LUN:
  1. Expand the existing LUN in 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 just used for reference.
Some third-party software, which is not deployed by Huawei, is used on the host during the capacity expansion. Huawei does not receive any information about the software and thereby cannot help the customer to assess potential risks. Based on 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.
The known potential risks in expanding LUN capacity include but are not limited to:
  • It is risky to expand LUN capacity on the host (that is, expand the volume and file system capacity of the host), and the risks are existed for all storage vendors, not just for Huawei.
  • Each operating system, file system, or volume management software has a specific limit for 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 the partition table, it is highly risky to expand LUN capacity, which may damage the partition table 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 the database, LUN capacity expansion may disorder metadata, leading to data inconsistency or loss.
  • For application software, the impact of LUN capacity expansion cannot be determined due to its various types and complex scenarios.

Understanding the Expansion Process

Before the expansion, read the following expansion procedure. Before the expansion, be familiar with the expansion procedure.

Figure 5-1 shows the storage space expansion procedure.

Figure 5-1  Capacity expansion process

Table 5-3 describes each step of expanding storage space.

Table 5-3  Steps for expanding storage space

Procedure

Operation

Description

Performing the Pre-expansion Check

Perform the pre-expansion check.

Before expanding the storage space, 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.

Locating a LUN to Be Expanded

Locate a LUN to be expanded.

Before expanding a LUN for storage services, confirm information about the LUN where current service data resides to ensure successful LUN expansion.

Expanding a LUN on the Storage System

Expand a LUN on the storage system.

Expand the LUN online to provide the required storage capacity.

Expanding Storage Space for an Application Server

Expand storage space for an application server.

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

Performing the Pre-expansion Check

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

Prerequisites

  • You can log in to the DeviceManager management interface 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 on the storage system.
  • Ensure that no data protection policy is configured for the LUN you want to expand.

Procedure

  1. Log in to the DeviceManager as the super administrator. Make sure that the storage environment meets the expansion requirement.
    1. In the Basic Information area of the Home page, check 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 device becomes normal.

    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 the 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 right navigation bar of the 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 state is normal.

      If an alarm is found, handle it in time based on the alarm information and handling suggestion.

    5. In the Mapped LUN area of Details, 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 LUN area, click and choose WWN or Host LUN ID from the drop-down list. The LUN WWN or host LUN ID is displayed.

Locating a LUN to Be Expanded

Before expanding a LUN for storage services, determine information about the LUN where current service data resides to ensure successful LUN expansion.

Prerequisites

  • If a Fibre Channel network is used, ensure that the world wide name (WWN) of a Fibre Channel initiator has been obtained.
  • If an Internet Small Computer Systems Interface (iSCSI) network is used, ensure that the iSCSI qualified name (IQN) of an iSCSI initiator has been obtained.
  • The UltraPath software has been installed on the host.

Context

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 show the host corresponding to the WWN or iSCSI IQN.

      Parameter

      Description

      Value

      initiator_type=? Type of an initiator

      Possible values are as follows:

      • iSCSI: iSCSI initiator
      • FC: Fibre Channel initiator
      wwn=? WWN of a Fibre Channel initiator. This parameter is available 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 is available only when initiator_type=? is iSCSI.

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

      admin:/>show initiator initiator_type=FC wwn=21000024ff53b640
      
      WWN               : 21000024ff53b640
      Running Status    : Online
      Free              : Yes
      Alias             : suse2_01
      Host ID           : 2
      Multipath Type    : Default
      

      The value of Host ID is the ID of a 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 a host.

      admin:/>show host lun host_id=2
      LUN ID LUN Name Host LUN ID
      ------ -------- -----------
      34 lun_0000 4
      35 lun_0001 5
      36 lun_0002 6

      The value of LUN ID is the ID of a LUN mapped to the host in 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. On the host where UltraPath is installed, run show vlun to view the WWN of a disk on the host.

      NOTE:
      For details about how to query WWNs of LUNs on other operating systems, see the User Guide of UltraPath specific to the operating systems.

  3. Check whether the two WWNs are the same. If they are the same, you can determine that the LUN is the one to be expanded.

    NOTE:

    For details about the preceding commands, see the OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003 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.
  • A LUN for which Snapshot, LUN Copy, SmartMigration, HyperMirror, Clone is configured cannot be expanded.

Procedure

  1. In the navigation tree on the right, click Provisioning.
    The Provisioning page is displayed.
  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 an Application Server

A LUN must be expanded when its capacity is insufficient to meet service requirements. An application server can use an expanded LUN only after required configurations are performed on the application server.

Expanding a LUN on an Application Server in Windows

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running Windows Server 2008 as an example to describe how to expand a LUN on an application server. For application servers running other versions of Windows operating systems, adjust the operations based on actual conditions.

Prerequisites

A LUN has been expanded on the storage system.

Context

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

Procedure

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

    The Server Manager dialog box is displayed.

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

    After the scanning is complete, the system displays the result as shown in Figure 5-2. On the right of disk G, the capacity of the partition to be expanded is displayed.
    Figure 5-2  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-3.
    Figure 5-3  Extend Volume Wizard

  5. Click Next.

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

    NOTE:
    • Disk 3 is the disk mapped from the LUN to be expanded on the application server.
    • You can change the expansion storage space in Select the amount of space in MB to suit your need. By default, the maximum storage space is used.

  6. Click Next.
  7. Click Finish.

    The Server Manager dialog box is displayed. You have completed configuring LUN expansion on the application server.

Result

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

Expanding a LUN on an Application Server in SUSE

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running SUSE 11.0 as an example to describe how to expand a LUN on an application server. For application servers running other versions of SUSE operating systems, adjust the operations based on actual conditions.

Prerequisites

A LUN has been expanded on the storage system.

Context

In the example of the section, the capacity of the LUN to be expanded is 25 GB and it will be expanded to 50 GB. The drive letter of the mapped disk on the application server is sdf.

Procedure

  1. Scan for disks on the SUSE-based application server.
    1. Scan for disks.

      • If the UltraPath software is installed, run hot_add command.
      • If the UltraPath software is not installed, perform the following operations:
        1. Run lsscsi to obtain the ID of the host where the LUN resides. 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 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 on the application server. The actual drive letter may be different.

  2. Run fdisk -l to view the 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. To add the file system of the LUN to the new storage space, run resize2fs /dev/sdf.

    • 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 a LUN in SUSE

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This section uses SUSE 11.0 as an example to describe how to non-disruptively expand a LUN 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 expansion has completed on the storage system.
  • A physical volume to be expanded has been determined.

Context

In the example of the section, sdb5 is a physical volume in the drive letter of the disk mapped from the LUN on the application server. The primal capacity of sdb5 is 104 MB, and the capacity after expansion is 120 MB.

Procedure

  1. On the application server, view 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 a LUN and Disk is the drive letter of a disk mapped from the LUN on the application server.

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

    NOTE:

    sdb5 is a physical volume in the drive letter of the disk mapped from the LUN on the application server. Adjust configuration operations based on an actual physical volume to be expanded.

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

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

    testlv is a 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 a LUN on an Application Server in RedHat

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running Red Hat 6.4 as an example to describe how to expand a LUN on an application server. For application servers running other versions of RedHat operating systems, adjust the operations based on actual conditions.

Prerequisites

A LUN has been expanded on the storage system.

Context

In the example of the section, the capacity of the LUN to be expanded is 25 GB and it will be expanded to 50 GB. The drive letter of the mapped disk on the application server is sdh. The actual drive letter may be different in practice.

Procedure

  1. Scan for disks on the RedHat-based application server.
    1. Scan for disks.

      • If the UltraPath software is installed, run hot_add command.
      • If the UltraPath software is not installed, perform the following operations:
        1. Run lsscsi command to obtain the ID of the host where the LUN resides. 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 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/sdh/device/rescan command to rescan for disks.

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

  2. Run fdisk -1 to view the 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. To add the file system of the LUN to the new storage space, run resize2fs /dev/sdh.

    [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 a LUN on an Application Server in Solaris

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running Solaris 10 as an example to describe how to expand a LUN on an application server. For application servers running other versions of Solaris operating systems, adjust the operations based on actual conditions.

Prerequisites

  • A LUN 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-based 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 corresponding disks of the LUN that you want to expand on the application server.

    /mnt/ indicates the mount directory of disks of 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 driver letter mapped by the LUN to the application server.

  4. After Specify disk (enter its number), enter the corresponding ID 3 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 a LUN on an Application Server in AIX

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running AIX 6.1 as an example to describe how to expand a LUN on an application server. For application servers running other versions of AIX operating systems, adjust the operations based on actual conditions.

Prerequisites

A LUN has been expanded on the storage system.

Context

In the example of the section, 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 that you want to expand 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-based 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, run rmdev -dl diskName to delete disk information and perform the follow-up operations. In the command, diskName indicates the disk of 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 lsdev -Cc disk command to view the information about 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, run the upadm show lun command to check 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 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, if the unit is MB, the capacity is 51,200 MB (50 GB) that is the same as the expansion result displayed on the storage system.

  5. Refresh the capacity of the volume group corresponding to the LUN that you want to expand.
    1. Run chvg -g vg1 to refresh the volume group of the LUN that you want to expand.

      # 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 to view parameters related to the volume group.

      # 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. If you want to create or modify a logical volume, you need to refer to the parameter to determine the size of the logical volume. In the example of this section, the value of PP SIZE is 32 MB.

  6. Modify the capacity of the logical volume to meet the need for expanding the file system.
    1. Run lslv lv1 to view parameters related to the logical volume.

      # 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 on the volume group. Pay attention to the MAX LPs, LPs, and PP SIZE parameters in the command output, as these values 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 the example of this section, 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 need to 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 need to adjust the maximum number of logical partitions to ensure that the capacity of the logical volume is equal to or larger than 48 GB. For example, if the capacity of the file system needs to be expanded to 48 GB (49,152 MB), the maximum number of logical partitions must be not smaller than 1536 (49,152/32).

    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.
  7. Expand the file system on the lv1 logical volume. Run chfs -a size=48G /mnt/lv1 to expand the file system of the volume group.

    # 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.

Expanding a LUN on an Application Server in HP-UX

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running HP-UX 11i v3 as an example to describe how to expand a LUN on an application server. For application servers running other versions of HP-UX operating systems, adjust the operations based on actual conditions.

Prerequisites

  • A LUN has been expanded on the storage system.
  • Services on the LUN to be expanded have been stopped.

Context

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

Procedure

  1. Scan for LUNs on the HP-UX-based application server.
    1. Run ioscan command to scan for hardware.
    2. Run ioscan -funNC disk to view 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 view 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 view the file system capacity after it is expanded.

    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 a LUN on an Application Server in VMware ESX

After expanding a LUN on its storage system, perform the expansion configuration on the corresponding application server for it to identify and use the expanded storage space. This task uses an application server running VMware ESXi 5.1.0 as an example to describe how to expand a LUN on an application server. For application servers running other versions of VMware ESX operating systems, adjust the operations based on actual conditions.

Prerequisites

A LUN has been expanded on the storage system.

Context

In this example of the section, the capacity of the LUN to be expanded is 25 GB and it will be expanded to 50 GB. The ID of the LUN to be expanded is 14.

Procedure

  1. In vSphere Client, click the Configuration tab.
  2. On the left navigation bar, click Storage.
  3. On the Storage page, click the Devices tab.

    On the Devices page, view the device mapped from the LUN to be expanded on the application server, as shown in Figure 5-6.
    Figure 5-6  Device mapped from the LUN to be expanded on the application server

  4. On the Devices page, click Rescan All.

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

    Figure 5-7  Rescan 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-8, the scanning is ongoing.
      Figure 5-8  Scanning ongoing

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

  6. On the Storage page, click the Datastores tab.

    On the Datastores page, view the datastore mapped from the LUN to be expanded on the application server, as shown in Figure 5-10.
    Figure 5-10  Device 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 Properties from the shortcut menu.

    The DataStore_Extend Properties dialog box is displayed, as shown in Figure 5-11.
    Figure 5-11  DataStore_Extend Properties dialog box

  8. In the Volume Properties area, click Increase.

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

  9. Select the datastore corresponding to the LUN to be expanded and click Next.
  10. View the current disk distribution and click Next.
  11. Set the size of the expansion data area. The maximum storage space is recommended, as shown in Figure 5-13. Click Next.

    Figure 5-13  Setting the size of the expansion data area

  12. Click Finish.

    The DataStore_Extend Properties dialog box is displayed.

  13. Click Close.

Result

  • On the Datastores tab of Storage page, view the expanded datastore, as shown in Figure 5-14.
    Figure 5-14  Datastore mapped from the expanded LUN on the application server

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

Translation
Download
Updated: 2019-04-17

Document ID: EDOC1000084191

Views: 86149

Downloads: 2300

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