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

Advanced O&M Command Reference

OceanStor 18000 V3 Series V300R006

This document is applicable to OceanStor 18500 V3 and 18800 V3. Based on the CLI, this document describes how to use various commands classified by functionsand how to set the CLI and manage the storage system through these commands. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.
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).
change storage_pool repair_lun

change storage_pool repair_lun

Function

The change storage_pool repair_lun command is used to repair a LUN.

Format

change storage_pool repair_lun disk_domain_id=? lun_id=? action=? [ scan_grain=? ] [ repair_extent_type=? ] [ repair_grain_type=? ] [ force=? ] [ repair_mode=? ] [ meta_type=? ]

Parameters

Parameter

Description

Value

disk_domain_id=?

Disk domain ID.

To obtain the value, run the "show disk_domain general" command in the guest view.

lun_id=?

LUN ID.

To obtain the value, run the "show lun general" command in the guest view.

action=?

Operation.

The value can be "repair", "repair_confirm", "repair_cancel","repair_reclaim", "repair_terminate" or "repair_verify", where:

  • "repair": to repair the LUN.
  • "repair_confirm": to confirm the repair.
  • "repair_cancel": to cancel the repair.
  • "clear_state": to clear the repair state.
  • "repair_reclaim": to reclaim idle Extents on the LUN.
  • "repair_terminate": to stop the repair or reclaim.
  • "repair_verify": to verify the LUN.

scan_grain=?

Whether the function of scanning for grain during the repair of a thin LUN is enabled.

The value can be "enable" or "disable", where:

  • "enable": The function of scanning for the grain is enabled.
  • "disable": The function of scanning for the grain is disabled.

force=?

Whether to perform forcible repair LUN.

The value can be "no" or "yes", where:

  • no: not to perform forcible repair.
  • yes: to perform forcible repair.

repair_extent_type=?

Specifies the metadata restoration policy at the extent layer for the restoration of thin LUNs and thick LUNs.

The value can be "scan_data_extent_tree", "scan_data_extent_backup", or "scan_data_extent_tree_nmgr". By default, the system automatically selects these values in the following sequence:

  • "scan_data_extent_tree": scan and restoration based on the Data Extent tree.
  • "scan_data_extent_backup": scan and restoration based on the backup Data Extent tree.
  • "scan_data_extent_tree_nmgr": NMGR restoration based on the Data Extent tree.

repair_grain_type=?

Specifies the metadata restoration policy at the grain layer for the restoration of thin LUNs.

The value can be "scan_grain_map_tree", "scan_grain_map_tree_nmgr", "scan_meta_extent_tree", "scan_meta_extent_backup". By default, the system automatically selects these values in the following sequence:

  • "scan_grain_map_tree": scan and restoration based on the Data Extent tree.
  • "scan_grain_map_tree_nmgr": scan and restoration based on the backup Data Extent tree.
  • "scan_meta_extent_tree": NMGR restoration based on the Data Extent tree.
  • "scan_meta_extent_backup": scan and restoration based on the backup Meta Extent.

repair_mode

Specifies the restoration mode.

The value can be "offline" or "online", where:

  • "offline": offline repair.
  • "online": online repair.

meta_type

Specifies the metadata type of online restoration.

The value can be "all", "cow" or "dcl", where:

  • "all": repair cow and dcl metadata.
  • "cow": repair cow metadata only.
  • "dcl": repair dcl metadata only.

Views

Developer view

Usage Guidelines

  • If "action=?" is set to "repair", specify the parameters of "scan_grain", "repair_extent_type" and "repair_grain_type". The default value of "scan_grain" is "disable".
  • "scan_grain", "repair_extent_type" and "repair_grain_type" are valid only when "action=?" is set to "repair".

Example

  • Repair LUN "0" in disk domain "0".
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=repair 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs).  
    Suggestion: Before you perform this operation,  
    1. ensure that host I/Os have been stopped.  
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y  
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>
  • Reclaim the idle metadata on LUN "0" in disk domain "0".
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=repair_reclaim 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs).  
    Suggestion: Before you perform this operation,  
    1. ensure that host I/Os have been stopped.  
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y  
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>
  • Stop the repairing or reclaiming of LUN "0" in disk domain "0".
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=repair_terminate 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs).  
    Suggestion: Before you perform this operation,  
    1. ensure that host I/Os have been stopped.  
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y  
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>
  • Cancel the repairing of LUN "0" in disk domain "0".
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=repair_cancel 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs).  
    Suggestion: Before you perform this operation,  
    1. ensure that host I/Os have been stopped.  
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y  
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>
  • Confirm the repairing of LUN "0" in disk domain "0".
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=repair_confirm 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs).  
    Suggestion: Before you perform this operation,  
    1. ensure that host I/Os have been stopped.  
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y  
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>
  • Clear the LUN repair state.
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=clear_state 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs).  
    Suggestion: Before you perform this operation,  
    1. ensure that host I/Os have been stopped.  
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y  
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>
  • Verify LUN "0" in disk domain "0".
    developer:/>change storage_pool repair_lun disk_domain_id=0 lun_id=0 action=repair_verify scan_grain=enable 
    DANGER: You are going to repair the metadata on a LUN. This operation will cause the LUN to go offline and change the metadata on the LUN. Performing this operation on a LUN for which snapshot and remote replication have been configured leads to COW data space leakage. During the execution process, config message cannot be used, so you cannot change the configuration information about the LUNs or disk domains (eg. create/delete LUNs). 
    Suggestion: Before you perform this operation, 
    1. ensure that host I/Os have been stopped. 
    2. ensure that this is the working controller of the LUN. 
    3. ensure that you enter the correct LUN ID. 
    Have you read danger alert message carefully?(y/n)y 
    Are you sure you really want to perform the operation?(y/n)y 
    Command execute successfully! 
    developer:/>

System Response

None

Translation
Download
Updated: 2019-07-12

Document ID: EDOC1000138389

Views: 485221

Downloads: 85

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