Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1009758.1
Update Date:2009-09-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  1009758.1 :   Sun StorEdge[TM] 9900 series: Unable to create Copy on Write (CoW) pairs with SIM 6001FF reported  


Related Items
  • Sun Storage 9990 System
  •  
  • Sun Storage 9985 System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Datacenter Disk
  •  

PreviouslyPublishedAs
213403


Symptoms

If SIM 6001FF occurs no further pairs can be created. SIM error codes 600yxx are related to CoW (copy-on-write) feature of Sun StorEdge[TM] 9990 series/Sun StorEdge[TM] 9985 System and pool utilization. They reflect over utilzation as follows:

6000xx - pool utilization exceeds set threshold value for the pool xx
6001xx - pool xx blocked because became full
6001FF - SM full (for pool usage)

If SIM 6001FF occures no further pairs can be created. The user will be notified.

SIM error code 4B3yxx means a failed copy-on-write snapshot pair; Copy-on-write Snapshot ERROR (abnormal end) where:

y = CU number
xx = LDEV number

SIM error codes 6001FF, 6001xx, 6000xx as well as 4B3yxx covered in TRBL18-20 and troubleshooting/recovery covered in TRBL18-50.



Resolution

1. Capture current Copy on Write, Shadow Image, True Copy and Universal Replicator configuration. You would need to recover them from that information later on. Refer to SunSolve article #81862 for more details.

2. Remove all COW pairs through either Storage Navigator or Command Control Interface (CCI).

3. Remove all Pools through Storage Navigator.

If the Storage Navigator denies to delete a Pool record the message id and review Storage Navigator Error Codes.

In the sample below message id 3005 58472 were reported.

messageID 3005 58472

The Operation of the pool has failed.

Pool cannot be registered when:

- V-VOL management area is not initialized.
- V-VOL management area is not installed.
- there is no space left in the V-VOL management area.
- the pool is blocked
- the state of shared memory is abnormal

Pool cannot be deleted when:

- V-VOL management area is not initialized.
- V-VOL management area is not installed.
- Copy-on-Write Snapshot pair still remains in the pool.
- P-VOL still remains in the pool
- the pool is blocked.

The threshold of pool cannot be changed when:

- the threshold is set below the usage rate of the pool.

At this point in time it is strongly recommended to consult Sun Support Services.



Additional Information

Please read and follow the instruction Copy-on-Write Snapshot User?s Guide, Command Control Interface (CCI) User and Reference Guide, Storage Navigator User?s Guide and Storage Navigator Error Codes.

Missing to initialize the VFS SYS Area and Pool Management Area were the root cause for the sample.



Product
Sun StorageTek 9900 ShadowImage In-System Replication
Sun StorageTek 9985 System
Sun StorageTek 9990 System

Internal Comments

ESC #1-18555406; Action plan by Matthias Muench, Germany.


Although the Copy-on-Write Snapshot User?s Guide states how to initialize the V-VOL management area and Pool Management Area there might be additional steps as installing Shared Memory and initialize the VFS SYS Area.


Following activities in the reference case after analyzing messageID 3005 58472.


1. Initialize VFS SYS Area

Depress Initialize button on Shadow Image Main panel.

- For Initialize, Insert Password of RAID-HOMRCF and select OK.

- Select OK to message "Do you want to execute the Initialize operation?(7010 9110)".

- Select OK to message "The requested operation is complete.(110 9002)".


2. Remove all CoW and Shadow Imgae pairs


3. Micro Code upgrade; please read and follow the ECN carefully.


4. Install additional Shared Memory if required; this step is optional.


5. Initialize VFS SYS Area and Pool Management Area.

If you discover stale pools verify that they have size=0 and no LDEVs associated. If so repeat to initialize VFS SYS Area and Pool Management Area.


6. Finally follow the "Copy-on-Write Snapshot Workflow" as documented in Copy-on-Write Snapshot User?s Guide.


It is strongly recommended to consult Storage TSC Highend Disk Backline for further advice and issue.


copy, on, write, shadow, image, cci, command, control, interface, cow, 9990, 9985, HDS, USP, NSC, v-vol, shared, memory, vfs sys area, micro, code
Previously Published As
87138

Change History
Date: 2007-01-25
User Name: 97961
Action: Approved
Comment: - Converted to STM formatting for better readability
- Made simple sentence/grammatical corrections
- Applied trademarking where it is missing
Version: 3
Date: 2007-01-25
User Name: 97961
Action: Accept
Comment:
Version: 0
Date: 2007-01-25
User Name: 90724
Action: Approved
Comment: Looks good.
Version: 0
Date: 2007-01-25
User Name: 90724
Action: Accept
Comment:
Version: 0
Date: 2007-01-05
User Name: 90779
Action: Approved
Comment: Completed draft although had no reply from the field engineer who applied the final action plan. I needed to translate from German to English and generalize the activities.

The general objective of this article is to make the customer aware of issues and to engage Sun Support Services. As there is very few experience with that product the Internal Only section covers further details.

Please keep that article as reference for Storage TSC backline engineers.
Version: 0
Date: 2006-10-06
User Name: 90779
Action: Created
Comment:
Version: 0
Product_uuid
590124a6-1b6f-4082-bb2c-c8d209ec464a|Sun StorageTek 9900 ShadowImage In-System Replication
73084edc-dc32-11d9-8a74-080020a9ed93|Sun StorageTek 9985 System
15644879-f179-11d8-ab63-080020a9ed93|Sun StorageTek 9990 System

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback