| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Sun Alert Sure Solution 1017437.1 : Access to Data on a Sun StorEdge T3/T3+ and Sun StorEdge 6120 Array May be Temporarily Lost When a Substituted Drive is Replaced
PreviouslyPublishedAs 228540 Product Sun StorageTek T3 Array Sun StorageTek T3+ Array Sun StorageTek 6120 Array Bug Id <SUNBUG: 4932057> Date of Resolved Release 01-APR-2005 Impact On a Sun StorEdge T3/T3+ or Sun StorEdge 6120 array, access to data may be lost when a drive that has previously failed (and has been logically disabled and substituted) is removed. The data will be inaccessible until the volume is remounted and any necessary recovery actions are performed on the host. Since the loss of access is abrupt, loss of data not yet committed to disk is possible. Contributing Factors This issue can occur in the following releases: SPARC Platform
The Sun StorEdge "ver" command at the T3, T3+ or 6120 system prompt can be used to determine the current firmware revision, as shown in the following example: 6120a:/:<1>ver 6120 Release 3.1.0 Fri Dec 19 14:49:54 PST 2003 (129.156.169.50) Copyright (C) 1997-2003 Sun Microsystems, Inc Note: In order for the described issue to occur, a drive failure must first result in the successful substitution of the hot spare followed by a second drive failure in the same RAID set. On a RAID 5 volume, this issue can occur if a second drive fails in any slot. On a RAID 1 volume, this issue will only occur if the second drive failure is adjacent to the first failed drive. Symptoms The "vol stat" command shows one drive substituted and another drive failed in a volume. When the drive in the substituted state is removed, the volume is unmounted. Workaround To work around the described issue, do the following: 1. Replace the second failed drive and keep the substituted drive in place. Do not remove the substituted drive until the reconstruction process is complete. 2. Replace the first failed drive which was substituted by the standby drive. The volume is fixed once this reconstruction process is complete. Note: Before replacing either failed drive, be sure to backup the data on the affected volume. Resolution This issue is addressed in the following releases: SPARC Platform
Note: The "Relief/Workaround" provided above is the final resolution for the Sun StorEdge T3 array. Modification History References<SUNPATCH: 115180-01><SUNPATCH: 115179-01> Previously Published As 101661 Internal Comments
Internal Contributor/submitter Steve.Chandler@sun.com Internal Eng Business Unit Group NWS (Network Storage) Internal Eng Responsible Engineer Christina.Tsui@Sun.COM Internal Services Knowledge Engineer jeff.folla@sun.com Internal Escalation ID 1-6901727 Internal Resolution Patches 115180-01, 115179-01 Internal Sun Alert Kasp Legacy ID 101661, 57751 (Sun Alert) Internal Sun Alert & FAB Admin Info Critical Category: Availability ==> Pervasive Significant Change Date: 2005-04-01 Avoidance: Patch, Workaround Responsible Manager: Lalit.Pathak@Sun.COM Original Admin Info: This document has been imported from KMS Creator and may need adjustment before re-publishing. This imported document has been reviewed/adjusted by: Review Name: Review Date: Original KMS Creator attributes below: --- PLEASE DO NOT MAKE ANY CHANGES BELOW THIS LINE! --- Sun Alert ID: 57751 Synopsis: Access to Data on a Sun StorEdge T3/T3+ and Sun StorEdge 6120 Array May be Temporarily Lost When a Substituted Drive is Replaced Category: Availability Product: Sun StorEdge T3/T3+, Sun StorEdge 6120 Array BugIDs: 4932057 Avoidance: Workaround, Patch State: Resolved Date Released: 01-Apr-2005 Date Closed: 01-Apr-2005 Date Modified: Escalation IDs: 1-6901727 Pending Patches: Resolution Patches: 115180-01, 115179-01 FIN: FCO: Date Submitted: 21-Feb-2005, 28-Feb-2005, 08-Mar-2005, 23-Mar-2005 Submitter: Steve.Chandler@sun.com Responsible Engineer: Christina.Tsui@Sun.COM Responsible Manager: Lalit.Pathak@Sun.COM CTE group: NWS Responsible Writer: jeff.folla@sun.com Distribution: Public SunSolve Workflow History: WF State: Issued, 05-Apr-2005, Jeff Folla WF Note: This Sun Alert was resolved at the time it was released. Updated the sun alert accordingly. WF State: Issued, 01-Apr-2005, David Mariotto WF Note: rcvd final from submitter, release to "Contract" WF State: Draft, 01-Apr-2005, David Mariotto WF Note: rcvd final from submitter, release to "Contract" WF State: Draft, 30-Mar-2005, Jeff Folla WF Note: Sent to BU and 24 hour review WF State: Draft, 29-Mar-2005, Jeff Folla WF Note: Waiting for approval from submitter and responsible engineer. WF State: Draft, 28-Mar-2005, Jeff Folla WF Note: Received an email with the requested information. Sent to submitter for review. Will send to 24 hour review upon approval. WF State: Draft, 23-Mar-2005, Jeff Folla WF Note: Sent email to the submitter requesting patch numbers and firmware versions for the affected platforms. WF State: Draft, 09-Mar-2005, Jeff Folla WF Note: Article created. Exported from KMS Creator Sat May 21 09:17:11 2005 GMT, olaf.reineke@sun.com Internal SA-FAB Eng Submission Access to Data on a Sun StorEdge T3/T3+ and Sun StorEdge 6120 Array May be Temporarily Lost When a Substituted Drive is Replaced Product_uuid 2a6d7d50-0a18-11d6-8e0b-f0bd33b24928|Sun StorageTek T3 Array 2a714b10-0a18-11d6-86e2-d56b387d4fbf|Sun StorageTek T3+ Array 2cd2e7d2-2980-11d7-9c3f-c506fe37b7ef|Sun StorageTek 6120 Array ReferencesSUNPATCH:115179-01SUNPATCH:115180-01 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||