Disk Enclosures
1751976 Members
4388 Online
108784 Solutions
New Discussion юеВ

How to stop the OPTIMIZING status

 
SOLVED
Go to solution
Daniel Sanabria
Advisor

How to stop the OPTIMIZING status

Hi,

When checking the array status under operations in progress it says "The array is OPTIMIZING" ... How can I stop this operation?

# armdsp -a 00SG217J0057


Vendor ID:______________________________HP
Product ID:_____________________________A6188A
Array World Wide Name:__________________50060b000014e1c0
Array Serial Number:____________________00SG217J0057
Alias:__________________________________va7100
Software Revision:______________________1.09.02 - 0191 - 060113
Command execution timestamp:____________Jun 21, 2007 10:05:34 AM
------------------------------------------------------------

ARRAY INFORMATION

Array Status:_________________________Ready
Firmware Revision:____________________38370HP13P0912011411
Product Revision:_____________________HP13
Last Event Log Entry for Page 1:______5425552

ENCLOSURES

Enclosure at M
Enclosure ID__________________________0
Enclosure Status______________________Good
Enclosure Type________________________HP StorageWorks Virtual Array 7100
Node WWN______________________________50060b000014e1c0

FRU HW COMPONENT IDENTIFICATION ID STATUS
===========================================================================
M Enclosure 00SG217J0057 Good
M/P1 Power Supply 94020HC01708 Good
M/P2 Power Supply 94020HC01709 Good
M/MP1 MidPlane 000599090901 Good
M/C2 Controller 00PR05A53401 Good
M/C2.H1 Host Port Good
M/C2.J1 BackEnd Port Good
M/C2.G1 Host GBIC A28B2AX Good
M/C2.B1 Battery 25766:MOLTECHPS:NI2040:2001/12/ Good
M/C2.PM1 Processor HP:A6188A:HP13 Good
M/C2.M1 DIMM 256 Good
M/C1 Controller 00PR04039675 Good
M/C1.H1 Host Port Good
M/C1.J1 BackEnd Port Good
M/C1.G1 Host GBIC A28BFKW Good
M/C1.B1 Battery 28040:MOLTECHPS:NI2040:2002/3/12 Good
M/C1.PM1 Processor HP:A6188A:HP13 Good
M/C1.M1 DIMM 256 Good
M/D1 Disk 3FP0NS5Q Good
M/D2 Disk 3FP0MBF2 Good
M/D3 Disk 3FP0PAE2 Good
M/D4 Disk 3FP0PCYX Good
M/D5 Disk 3FP0NTVT Good
M/D6 Disk 3CD0SYV3 Good

CONTROLLERS

Controller At M/C2:
Status:_______________________________Good
Serial Number:________________________00PR05A53401
Vendor ID:____________________________HP
Product ID:___________________________A6188A
Product Revision:_____________________HP13
Firmware Revision:____________________38370HP13P0912011411
Manufacturing Product Code:___________IJMTU00008
Controller Type:______________________HP StorageWorks Virtual Array 7100
Battery Charger Firmware Revision:____4.3
Front Port At M/C2.H1:
Status:_____________________________Good
Port Instance:______________________0
Hard Address:_______________________126
Link State:_________________________Link Up
Node WWN:___________________________50060b000014e1c0
Port WWN:___________________________50060b00002681bc
Topology:___________________________Point To Point, Fabric Attached
Data Rate:__________________________1 GBit/sec
Port ID:____________________________0x11200
Device Host Name:___________________bob
Hardware Path:______________________0/10/0/0.1.18.0.0.0.0
Device Path:________________________/dev/dsk/c5t0d0
Host GBIC at M/C2.G1:
Status:_____________________________Good
Identification:_____________________A28B2AX
Battery at M/C2.B1:
Status:_____________________________Good
Identification:_____________________25766:MOLTECHPS:NI2040:2001/12/
Manufacturer Name:__________________MOLTECHPS
Device Name:________________________NI2040
Manufacturer Date:__________________December 13, 2001
Remaining Capacity:_________________5289 mAh
Remaining Capacity:_________________88 %
Voltage:____________________________12331 mVolts
Discharge Cycles:___________________1
Processor at M/C2.PM1:
Status:_____________________________Good
Identification:_____________________HP:A6188A:HP13
DIMM at M/C2.M1:
Status:_____________________________Good
Identification:_____________________256
Capacity:___________________________256 MB

Controller At M/C1:
Status:_______________________________Good
Serial Number:________________________00PR04039675
Vendor ID:____________________________HP
Product ID:___________________________A6188A
Product Revision:_____________________HP13
Firmware Revision:____________________38370HP13P0912011411
Manufacturing Product Code:___________IJMTU00008
Controller Type:______________________HP StorageWorks Virtual Array 7100
Battery Charger Firmware Revision:____4.3
Front Port At M/C1.H1:
Status:_____________________________Good
Port Instance:______________________0
Hard Address:_______________________126
Link State:_________________________Link Up
Node WWN:___________________________50060b000014e1c0
Port WWN:___________________________50060b0000146462
Topology:___________________________Unknown
Data Rate:__________________________1 GBit/sec
Port ID:____________________________0
Device Host Name:___________________bob
Hardware Path:______________________Unknown
Device Path:________________________Unknown
Host GBIC at M/C1.G1:
Status:_____________________________Good
Identification:_____________________A28BFKW
Battery at M/C1.B1:
Status:_____________________________Good
Identification:_____________________28040:MOLTECHPS:NI2040:2002/3/12
Manufacturer Name:__________________MOLTECHPS
Device Name:________________________NI2040
Manufacturer Date:__________________March 12, 2002
Remaining Capacity:_________________4895 mAh
Remaining Capacity:_________________81 %
Voltage:____________________________12608 mVolts
Discharge Cycles:___________________1
Processor at M/C1.PM1:
Status:_____________________________Good
Identification:_____________________HP:A6188A:HP13
DIMM at M/C1.M1:
Status:_____________________________Good
Identification:_____________________256
Capacity:___________________________256 MB

PORTS

Settings for port M/C2.H1:
Port ID:______________________________108
Behavior:_____________________________HPUX
Topology:_____________________________Point To Point, Fabric Attached
Queue Full Threshold:_________________750
Data Rate:____________________________1 GBit/sec

Settings for port M/C1.H1:
Port ID:______________________________110
Behavior:_____________________________HPUX
Topology:_____________________________Point To Point, Fabric Attached
Queue Full Threshold:_________________750
Data Rate:____________________________1 GBit/sec

DISKS

Disk at M/D1:
Status:_______________________________Good
Disk State:___________________________Included
Vendor ID:____________________________HP 36.4G
Product ID:___________________________ST336605FC
Product Revision:_____________________HP08
Data Capacity:________________________33.378 GB (70000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________111
Node WWN:_____________________________20000004cf2f34f0
Initialize State:_____________________Ready
Redundancy Group:_____________________1
Volume Set Serial Number:_____________0000179100000006
Serial Number:________________________3FP0NS5Q
Firmware Revision:____________________HP08

Disk at M/D2:
Status:_______________________________Good
Disk State:___________________________Included
Vendor ID:____________________________HP 36.4G
Product ID:___________________________ST336605FC
Product Revision:_____________________HP08
Data Capacity:________________________33.378 GB (70000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________112
Node WWN:_____________________________20000004cf27c907
Initialize State:_____________________Ready
Redundancy Group:_____________________1
Volume Set Serial Number:_____________0000179100000006
Serial Number:________________________3FP0MBF2
Firmware Revision:____________________HP08
Recovery Maps are on this disk.

Disk at M/D3:
Status:_______________________________Good
Disk State:___________________________Included
Vendor ID:____________________________HP 36.4G
Product ID:___________________________ST336605FC
Product Revision:_____________________HP08
Data Capacity:________________________33.378 GB (70000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________113
Node WWN:_____________________________20000004cf2f7f76
Initialize State:_____________________Ready
Redundancy Group:_____________________1
Volume Set Serial Number:_____________0000179100000006
Serial Number:________________________3FP0PAE2
Firmware Revision:____________________HP08

Disk at M/D4:
Status:_______________________________Good
Disk State:___________________________Included
Vendor ID:____________________________HP 36.4G
Product ID:___________________________ST336605FC
Product Revision:_____________________HP08
Data Capacity:________________________33.378 GB (70000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________114
Node WWN:_____________________________20000004cf2f7f61
Initialize State:_____________________Ready
Redundancy Group:_____________________1
Volume Set Serial Number:_____________0000179100000006
Serial Number:________________________3FP0PCYX
Firmware Revision:____________________HP08
Recovery Maps are on this disk.

Disk at M/D5:
Status:_______________________________Good
Disk State:___________________________Included
Vendor ID:____________________________HP 36.4G
Product ID:___________________________ST336605FC
Product Revision:_____________________HP08
Data Capacity:________________________33.378 GB (70000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________115
Node WWN:_____________________________20000004cf2f348d
Initialize State:_____________________Ready
Redundancy Group:_____________________1
Volume Set Serial Number:_____________0000179100000006
Serial Number:________________________3FP0NTVT
Firmware Revision:____________________HP08

Disk at M/D6:
Status:_______________________________Good
Disk State:___________________________Included
Vendor ID:____________________________HP 36.4G
Product ID:___________________________ST336704FC
Product Revision:_____________________HP12
Data Capacity:________________________33.378 GB (70000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________116
Node WWN:_____________________________200000203742d2a0
Initialize State:_____________________Ready
Redundancy Group:_____________________1
Volume Set Serial Number:_____________0000179100000006
Serial Number:________________________3CD0SYV3
Firmware Revision:____________________HP12

LUNS

LUN 0:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________20 MB
WWN:__________________________________50060b000014e1c00000000000000007
Number Of Business Copies:____________0

LUN 1:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________8 GB
WWN:__________________________________50060b000014e1c0000100000000000c
Number Of Business Copies:____________0

LUN 2:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________24 GB
WWN:__________________________________50060b000014e1c0000200000000000d
Number Of Business Copies:____________0

LUN 3:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________24 GB
WWN:__________________________________50060b000014e1c0000300000000000e
Number Of Business Copies:____________0

LUN 4:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________24 GB
WWN:__________________________________50060b000014e1c0000400000000000f
Number Of Business Copies:____________0

LUN 5:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________7 GB
WWN:__________________________________50060b000014e1c00005000000000010
Number Of Business Copies:____________0

LUN 7:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________9 GB
WWN:__________________________________50060b000014e1c00007000000000015
Number Of Business Copies:____________0

LUN 8:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________10.895 GB
WWN:__________________________________50060b000014e1c00008000000000016
Number Of Business Copies:____________0

LUN 66:
Redundancy Group:_____________________1
Active:_______________________________True
Data Capacity:________________________7.218 GB
WWN:__________________________________50060b000014e1c00042000000000012
Number Of Business Copies:____________0

CAPACITY Totals for Redundancy Group 1:
REGULAR LUNs:_________________________114.132 GB
BUSINESS COPIES:______________________0 bytes

CAPACITY USAGE

Total Disk Enclosures:________________1

Redundancy Group:_____________________1
Total Disks:________________________6
Total Physical Size:________________200.271 GB
Allocated to Regular LUNs:__________114.132 GB
Allocated as Business Copies:_______0 bytes
Used as Active Hot Spare:___________0 bytes
Used for Redundancy:________________77.138 GB
Unallocated (Available for LUNs):___9 GB

SUB-SYSTEM SETTINGS

RAID Level:___________________________HPAutoRAID
Auto Format Drive:____________________On
Capacity Depletion Threshold:_________100%
Queue Full Threshold Maximum:_________8192
Enable Optimize Policy:_______________True
Enable Manual Override:_______________False
Manual Override Destination:__________False
Read Cache Disable:___________________False
Rebuild Priority:_____________________Low
Security Enabled:_____________________False
Shutdown Completion:__________________0
Subsystem Type ID:____________________0
Unit Attention:_______________________True
Volume Set Partition (VSpart):________False
Write Cache Enable:___________________True
Write Working Set Interval:___________8640
Enable Prefetch:______________________False
Disable Secondary Path Presentation:__False

RESILIENCY SETTINGS

Simplified Resiliency Setting:________Normal Performance (Default)
Enable Secure Mode:___________________True
Disable NVRAM on UPS Absent:__________False
Disable NVRAM on WCE False:___________False
Disable Read Hits:____________________False
Force Unit Access Response:___________1
Lock Write Cache On:__________________True
Performance Goal Configuration:_______Normal Performance
Resiliency Threshold:_________________4
Single Controller Warning:____________True

DISK SETTINGS

Auto Include:_________________________On
Auto Rebuild:_________________________On
Hot Spare:____________________________None
Max Drives per Loop Pair:_____________15
Max Drives per Subsystem:_____________15

ENCLOSURE SETTINGS

Max Enclosures per Loop Pair:_________0
Max Enclosures per Subsystem:_________0

LUN SETTINGS

LUN Creation Limit:___________________128
Maximum LUN Creation Limit:___________128
Migrating Write Destination:__________False

SCRUB SETTINGS

Scrub Restart Period:_________________7190 minutes
Scrub State:__________________________Paused or pre-empted by a higher priority policy

OPERATIONS IN PROGRESS

The array is OPTIMIZING.

WARNINGS

None
7 REPLIES 7
Torsten.
Acclaimed Contributor
Solution

Re: How to stop the OPTIMIZING status

The array is balancing the data across the disks - this is normal, no need to stop it.

But I noticed the firmware is pretty old:
Product Revision:_____________________HP13

Consider to upgrade to the latest (HP22).

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: How to stop the OPTIMIZING status

from the manual:

"The optimization policy manages the movement of data within the array
between RAID 1+0 and RAID 5DP. The distribution of data is intended to
provide optimum performance and should be left enabled in most
situations.
When optimization is enabled, data will be moved from RAID 5DP to
RAID 1+0 when necessary to improve performance. Disabling
optimization will stop the migration of data from RAID 5DP to RAID 1+0."

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Daniel Sanabria
Advisor

Re: How to stop the OPTIMIZING status

Does this means that it'll OPTIMIZING forever (or most of the time)?

Thanks for your answer,

Daniel
Torsten.
Acclaimed Contributor

Re: How to stop the OPTIMIZING status

If optimizing is needed and the array is idle it will optimize.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Daniel Sanabria
Advisor

Re: How to stop the OPTIMIZING status

Thanks Torsten,

The whole point is that we're having serious problems when we loose a disk and the array goes into REBUILD (not OPTIMIZING, I'm just trying to learn here).

5 RP3440 are sharing the array and our application running on all 5 nodes is heavy in reading/writing activity.

when the array goes into REBUILD is almost like an outage since it appears that seek times on the disk are higher.

The questions now are, Is there a way to minimize the performance impact when the Array goes into REBUILD?

Having a hot-spare area will help in the performance impact? if so what you think should be the size?

thanks,

Daniel
Torsten.
Acclaimed Contributor

Re: How to stop the OPTIMIZING status

"The questions now are, Is there a way to minimize the performance impact when the Array goes into REBUILD?"

Yes, upgrade the firmware!

You can read in every release notes - performance improved.

"... There are several reliability and performance enhancements made to the firmware ..."


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Daniel Sanabria
Advisor

Re: How to stop the OPTIMIZING status

our test environment is certainly not up-to-date but I just check and in production we have HP22 installed.