Asset ID:	1-72-1009380.1
Update Date:	2009-04-15
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1009380.1 :   Sun StorEdge[TM] 6920: After Deleting Volumes and Pool, Vdisk Has a State of In-Use  


PreviouslyPublishedAs
212970

Symptoms
This issue is caused by having a mirrored volume with components in different pools.

Then, in an attempt to reclaim space by breaking a component, deleting it, and its parent pool.  Reference documents:
  <Document: 1002715.1>  Validating Sun StorEdge[TM] 6920 Mirror Volume Modification

  <Document: 1005385.1> Validating Sun StorEdge[TM] 6920 Volume Deletion

  <Document: 1009823.1> Validating Sun StorEdge[TM] 6920 Pool Deletion

The end result of these actions was a vdisk that was still in an In Use state and unable to use or reconfigure the space.  Reference document <Document: 1002889.1> Validating VDisk State and Details on a Sun StorEdge[TM] 6920

You will not be able to use the space because the associate pool is deleted.

You will not be able to delete the Vdisk, because the array still considers it In-Use

Resolution
The Vdisk cannot be deleted, due to the existence of mirror component log volumes that do not appear in the User Interface.

The Vdisk will return to a Not In-Use state if the last component of  the mirror volume is broken from the mirror.  This will change the volume type from Mirror to Single.

Reference documents:

 <Document: 1009974.1> Validating Volume State and Details on a Sun StorEdge[TM] 6920

 <Document: 1002715.1> Validating Sun StorEdge[TM] 6920 Mirror Volume Modification

To be able to use the space without deleting the Vdisk, Vdisk will need to be moved into a valid pool, as additional capacity.  Reference documents:

  <Document: 1008494.1> Validating Sun StorEdge[TM] 6920 VDisk Modification

  <Document: 1013066.1> Validating Sun StorEdge[TM] 6920 Pool Modification

  <Document: 1007144.1> Validating Pool State and Details on a Sun StorEdge[TM] 6920

Product
Sun StorageTek 6920 System
Sun StorageTek 6920 Maintenance Update 2
Sun StorageTek 6920 Maintenance Update 1

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

[email protected]

The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK.

in-use, vdisk, free space, mirror logs, unity, delete, pool, mirror, volume, 6920, system1, audited
Previously Published As
83377

Change History
Date: 2007-09-28
User Name: 7058
Action: Approved
Comment: OK to publish now
Version: 9
Date: 2007-09-26
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2007-09-26
User Name: 88109
Action: Approved
Comment: draft documents are making their or have made their way to final review.
Version: 0
Date: 2007-09-20
User Name: 7058
Action: Rejected
Comment: Jose,

I cannot publish this document until all dependent documents are in final review.

90362 - final review
90306 - draft
90464 - draft
90572 - draft
90246 - draft
90571 - draft
90465 - draft
90414 - draft

Once these documents make their way to final review, you can then resubmit this document to final review and I will then pubish the documents in a group.


Attachments

This solution has no attachment