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

Event Reference for File

OceanStor Dorado V3 Series V300R002

This document is applicable to OceanStor Dorado5000 V3, Dorado6000 V3 and Dorado18000 V3. This document describes the basic knowledge about the events of storage system in terms of event definition, event level, impact on the system, possible cause, and handling procedure.
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).
0x100F01250001 HyperVault Service Fails

0x100F01250001 HyperVault Service Fails

Description

The HyperVault service fails.

Applicable Model

Applicable to all models.

Attribute

ID

Event Type

Event Level

Automatically Cleared

0x100F01250001

Run Log

Major

No

Impact on the System

The data of the primary and secondary file systems is inconsistent.

Possible Causes

  • The HyperVault task is suspended because the link between the primary and secondary devices is down.
  • The HyperVault is unavailable because the status of the file system used for creating the HyperVault is abnormal.
  • The file system to which the HyperVault belongs has insufficient space, so the HyperVault service is faulty.
  • The number of user snapshots in the file system reaches the maximum system specifications.

Procedure

  1. Run the show remote_device general command to check whether the link between the primary and secondary devices of the HyperVault is down.

    1. If yes=> Step2.
    2. If no=> Step3.

  2. Reconnect the link between the primary and secondary devices and check whether the HyperVault is available.

    1. If yes, no further action is required.
    2. If no, and the link is normal, go to step3. If the link is abnormal, go to step7.

  3. Run the show file_system general file_system_id=X command to check whether the status of the file system to which the HyperVault belongs is normal and whether the file system has available space.

    1. If yes=> Step5.
    2. If no=> Step4.

  4. Clear the alarm by taking recommended actions in the alarm details of the file system in DeviceManager. If the remaining space in the file system is insufficient, expand the capacity. Then, check whether the HyperVault that belongs to the file system is available.

    1. If yes, no further action is required.
    2. If no=> Step5.

  5. Check whether the number of user snapshots in the file system to which the HyperVault belongs reaches the maximum system specifications.

    1. If yes=> Step6.
    2. If no=> Step7.

  6. Check whether the snapshots of the file system to which the HyperVault belongs can be deleted.

    1. If yes, delete the unnecessary snapshots.
    2. If no=> Step7.

  7. Collect related information and contact technical support engineers.
Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100076630

Views: 19503

Downloads: 5

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