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


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


Private Resource Pools of the S5000 R2 Storage Device Fail to be Deleted

Publication Date:  2012-07-18 Views:  82 Downloads:  0

Issue Description

Before a license file is imported to activate relevant value-added function of the S5000 R2 storage system, misoperating the Add private resource pools function on the disk array causes that the private resource pools fail to be deleted on the management interface. The private resource pools fail to be deleted unless the license file is imported to activate the value-added function. The customer who does not purchase the license needs to delete the private resource pools on the CLI.

Alarm Information


Handling Process

(Commands are highlighted in red and description is highlighted in green as follows.)

Step 1 Check the resource pools that contain private LUNs. OceanStor: admin> showpoollun -pi a (resource pools a and b) OceanStor: admin> showpoollun -pi b

 Step 2 Delete all private LUNs. OceanStor: admin> rmlunfrompool -i X (LUN IDs) -pi X (resource pool a or b) After the operation, log in to the Web page and find that the private resource pools are deleted and LUN resources are released.

Root Cause

It is a bug in the current OSM version. The bug will be rectified in the next version.


As a storage system has a complicated structure, unexpected faults may occur on each module. If the fault causes cannot be located on the graphical interface, locate the causes on the CLI.