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).
Making Storage Space Available (SUSE)

Making Storage Space Available (SUSE)

This section describes how to enable a SUSE-based application server to use the space of a storage system.

Procedure

  1. Log in to the SUSE-based application server as user root.
  2. Scan for the LUNs mapped to the application server.

    Use any of the following methods based on your networking mode.
    • iSCSI networking where UltraPath is not installed

      Run the /etc/init.d/open-iscsi restart command to restart the iSCSI service and scan for LUNs.

    • Fibre Channel networking where UltraPath is not installed
      NOTE:

      The following uses the QLA2460 Fibre Channel HBA as an example to explain how to scan for LUNs. For other Fibre Channel HBAs, refer to their manuals.

      1. Run the lsmod command to query the name of the Fibre Channel HBA driver.
        The following output is displayed.
        # lsmod
        Module                Size   Used by
        qla2xxx               293455  1
        autofs4              23749   2
        hidp                 23105   0
        rfcomm               42457   0

        The output shows that the name of the Fibre Channel HBA driver is qla2xxx.

      2. Run the rmmod command to deregister the Fibre Channel HBA driver.
        # rmmod qla2xxx

        In this example, the deregistered Fibre Channel HBA driver is qla2xxx.

      3. Run the modprobe command to reload the Fibre Channel HBA driver.
        # modprobe qla2xxx

        In this example, the reloaded Fibre Channel HBA driver is qla2xxx.

    • iSCSI or Fibre Channel networking where UltraPath is installed
      Run the hot_add command to scan for LUNs.
      # hot_add
      Starting new devices re-scan...
      delete LUN not mapped or mapping changed...
      scan unconfigured devices...
      scan qla2 HBA host /sys/class/scsi_host/host3...
              found 3:0:0:2 
      scan qla2 HBA host /sys/class/scsi_host/host4...
              found 4:0:0:2 
      scan iSCSI software initiator host /sys/class/scsi_host/host10...
              no new device found
      scan iSCSI software initiator host /sys/class/scsi_host/host12...
              no new device found
      run  /usr/sbin/upadm start busscan...
      scan mpp virtual host /sys/class/scsi_host/host8...
              found ->/dev/sdb 
      wait for syncing device reference count...
      wait for Lun report...
      found virtual host8
      /usr/sbin/hot_add is completed.
      

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

    The application server detects a LUN of 10.7 GB and named /dev/sdb, as shown in the following output:
    Disk /dev/sda: 79.5 GB, 79456894976 bytes
    255 heads, 63 sectors/track, 9660 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x225f225e
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1               1        1566    12578863+   7  HPFS/NTFS
    /dev/sda2            1567        1757     1534207+  82  Linux swap / Solaris
    /dev/sda3   *        1758        9660    63480847+  83  Linux
    
    Disk /dev/sdb: 10.7 GB, 10737418240 bytes
    64 heads, 32 sectors/track, 10240 cylinders
    Units = cylinders of 2048 * 512 = 1048576 bytes
    Disk identifier: 0x00000000
    
    Disk /dev/sdb doesn't contain a valid partition table
    
    NOTE:
    If no new logical disk is detected, troubleshoot the fault and rescan for logical disks. Possible faults include:
    • The application server is incorrectly connected to the storage system after the network cable has been removed and reinserted.
    • The link between the application server and storage system is down.
    • The rate of the Fibre Channel host port is inconsistent with that of the Fibre Channel HBA on the application server.
    • The HBA driver has been uninstalled.
    • The RAID is faulty.
    • Multipathing software is not installed or an incorrect version is installed.
    • The device file on the application server is lost.
    For details, see Failure to Discover LUNs by an Application Server in the OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3 Storage System V300R003 Troubleshooting.

  4. Run the fdisk command to partition the logical disk.

    For example, to create a primary partition for the /dev/sdb logical disk, run the following command.

    # fdisk /dev/sdb
    Command (m for help): n
    Command action
       e   extended
       p   primary partition (1-4)
    p
    Partition number (1-4): 1
    First cylinder (1-10240, default 1): 1
    Last cylinder, +cylinders or +size{K,M,G} (1-10240, default 10240): 10240
    
    Command (m for help): w
    The partition table has been altered!
    
    Syncing disks.
    
    NOTE:
    If the capacity of the LUN is larger than 2 TB, run the parted command to change it to the GPT type and then partition it.

  5. Create a file system on the logical disk.

    For example, to create an ext3 file system on the sdb1 logical disk, run the mkfs.ext3 /dev/sdb1 command. The following output is displayed.
    # mkfs.ext3 /dev/sdb1
    mke2fs 1.38 ( 30-Jun-2005 )
    Filesystem label=
    OS type: Linux
    Block size=1024 ( log=0 )
    Fragment size=1024 ( log=0 )
    78312 inodes , 313100 blocks
    15655 blocks ( 5.00% ) reserved for the super user
    First data block=1
    Maximum filesystem blocks=67633152
    39 block groups
    8192 blocks per group , 8192 fragments per group
    2008 inodes per group
    Superblock backups stored on blocks:
            8193 , 24577 , 40961 , 57345 , 73729 , 204801 , 221185
    
    Checking for bad blocks ( read-only test ): done                        100
    Writing inode tables: done
    Creating journal  ( 8192 blocks ): done
    Writing superblocks and filesystem accounting information: done
    
    This filesystem will be automatically checked every 23 mounts or
    180 days , whichever comes first.  Use tune2fs -c or -i to override.
    
    

  6. Create a file directory.

    Run the following command to create a file directory:
    # mkdir /directory
    In this example, the directory directory is created.

    After mounting logical disks, modify the /etc/fstab file, set automatic loading configuration items, and bond universally unique identifiers (UUIDs) to prevent automatic logical disk loading failures or drive letter changes when the application server is restarted. For details, contact your operating system supplier or system administrator.

  7. Mount the partitioned logical disk to the directory.

    Run the following command to mount the logical disk:

    mount /dev/sdb1 /directory
    
    In this example, the /dev/sdb1 logical disk is mounted to directory.

Result

Successful mounting ensures that the application server can read and write the logical disk as a normal disk. Run the mount command to check whether the logical disk is mounted correctly. If the following output is displayed, the mounting was successful:
# mount
/dev/sda2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw, gid=5, mode=620)
/dev/sda5 on /home type ext3 (rw)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
none on /proc/fs/vmblock/mountPoint type vmblock (rw)
/dev/hdc on /media/RHEL_5.3 i386 DVD type iso9660 (ro, noexec, nosuid, nodev, uid=0)
/dev/sdb1 on /directory type ext3 (rw)

LVM Management

Logical volume manager (LVM) can combine the space of several disks (physical volumes) into a volume group and divide the space of the volume group into logical volumes.

Use LVM as follows:

  1. Run the fdisk command to create an LVM partition.
    # fdisk /dev/sdc
    Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
    Building a new DOS disklabel with disk identifier 0x1c36ca92.
    Changes will remain in memory only, until you decide to write them.
    After that, of course, the previous content won't be recoverable.
    
    Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
    
    Command (m for help): p
    
    Disk /dev/sdc: 107.3 GB, 107374182400 bytes
    
    255 heads, 63 sectors/track, 13054 cylinders
    
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
    
       Device Boot      Start         End      Blocks   Id  System
    
    /dev/sdc1               1         200     1606468+  83  Linux
    
    /dev/sdc4             201        1000     6426000    5  Extended
    
    /dev/sdc5             201         400     1606468+  8e  Linux
    
    /dev/sdc6             401         600     1606468+  83  Linux
    
     
    
    Command (m for help): t
    
    Partition number (1-6): 5
    
    Hex code (type L to list codes): 8e
    
    Changed system type of partition 6 to 8e (Linux LVM)
    
     
    
    Command (m for help): t
    
    Partition number (1-6): 6
    
    Hex code (type L to list codes): 8e
    
    Changed system type of partition 6 to 8e (Linux LVM)
    
     
    
    Command (m for help): p
    
     
    
    Disk /dev/sdc: 107.3 GB, 107374182400 bytes
    
    255 heads, 63 sectors/track, 13054 cylinders
    
    Units = cylinders of 16065 * 512 = 8225280 bytes
    
     
    
       Device Boot      Start         End      Blocks   Id  System
    
    /dev/sdc1               1         200     1606468+  83  Linux
    
    /dev/sdc4             201        1000     6426000    5  Extended
    
    /dev/sdc5             201         400     1606468+  8e  Linux LVM
    
    /dev/sdc6             401         600     1606468+  8e  Linux LVM
    
  2. Run the pvcreate command to create a physical volume.
    # pvcreate /dev/sdc5
    
      Physical volume "/dev/sdc5" successfully created
    
    # pvcreate /dev/sdc6
    
      Physical volume "/dev/sdc6" successfully created
    
    After creating the physical volume, run the pvdisplay -v command to check whether the physical volume is created successfully.
  3. Run the vgcreate command to create a volume group.
    # vgcreate vg0 /dev/sdc5 /dev/sdc6
    
      Volume group "vg0" successfully created
    
  4. Run the lvcreate command to create a logical volume.
    # lvcreate -L 10m -n lv0 vg0
    
      Rounding up size to full physical extent 12.00 MB
    
      Logical volume "lv0" created
    
    After creating the logical volume, run the vgdisplay -v command to confirm the logical volume information.
  5. Run the mkfs.xx command to create a file system. The ext3 format is used as an example here.
    # mkfs.ext3 /dev/vg0/lv0 
    
    mke2fs 1.39 (29-May-2006)
    
    Filesystem label=
    
    OS type: Linux
    
    Block size=1024 (log=0)
    
    Fragment size=1024 (log=0)
    
    3072 inodes, 12288 blocks
    
    614 blocks (5.00%) reserved for the super user
    
    First data block=1
    
    Maximum filesystem blocks=12582912
    
    2 block groups
    
    8192 blocks per group, 8192 fragments per group
    
    1536 inodes per group
    
    Superblock backups stored on blocks: 
    
        8193
    
     
    
    Writing inode tables: done                            
    
    Creating journal (1024 blocks): done
    
    Writing superblocks and filesystem accounting information: done
    
     
    
    This filesystem will be automatically checked every 20 mounts or
    
    180 days, whichever comes first.  Use tune2fs -c or -i to override.
    
  6. Create a mount point to mount the logical volume.
    # mkdir /test/mnt1
    
    # mount /dev/vg0/lv0 /test/mnt1/
    
Translation
Download
Updated: 2019-04-17

Document ID: EDOC1000084191

Views: 86249

Downloads: 2300

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