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-77-1000006.1
Update Date:2011-03-01
Keywords:

Solution Type  Sun Alert Sure

Solution  1000006.1 :   Changing the Cache Optimization Mode Incorrectly on Sun StorEdge 3310, 3510 or 3511 May Cause Issues Affecting Filesystem Availability and Data Integrity  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3511 SATA Array
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Data Loss
  •  

PreviouslyPublishedAs
200007


Product
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3510 FC Array
Sun StorageTek 3511 SATA Array

Bug Id
<SUNBUG: 5069625>

Date of Workaround Release
15-SEP-2004

Date of Resolved Release
12-OCT-2005

Impact

Using sccli(1M) to change the cache optimization mode (sequential vs random) without first deleting all existing logical drives and then performing a reset of the array can affect filesystem availability and data integrity.


Contributing Factors

This issue can occur on the following platforms:

  • Sun StorEdge 3310 (SCSI) Array without sccli 1.6.2
  • Sun StorEdge 3510 FC Array without sccli 1.6.2
  • Sun StorEdge 3511 FC Array (SATA) without sccli 1.6.2

The RAID controller operates with the same stripe size for all logical drives and the optimization mode is dependent on any existing logical drives configured. Should the operator change the optimization mode (i.e., "sequential" to "random"), without deleting all existing logical drives and resetting the array, the operating mode is still at "sequential" even though the optimization mode displays as "random." Any subsequent logical drives created will be labeled as "random" mode, even though the active operating mode is "sequential," and any data written to the newly created logical drives will be written using "sequential" mode stripe size instead.

The next time the controller(s) is reset or power cycled, the operating mode now changes to "random," as determined by the metadata on the existing logical drive(s), and a data mismatch will occur. Since the data was initially written as "sequential" and now the operating mode is "random," the data presented back to the host will appear to be out of sequence and corrupted as the stripe size and access pattern have been changed.


Symptoms

Data presented to host applications will appear to be corrupted and out of sequence. Volume management applications may not be able to import disk groups and fsck(1M) will be unsuccessful.


Workaround

The proper procedures to change optimization mode without running into a data mismatch are:

  1. Back up data, if needed for later use
  2. Delete all existing logical drives
  3. Change optimization mode
  4. Reset or power cycle the array unit
  5. Create new logical drives

Resolution

This issue is resolved on the following platforms:

  • Sun StorEdge 3310 (SCSI) Array with sccli 1.6.2 or later
  • Sun StorEdge 3510 FC Array with sccli 1.6.2 or later
  • Sun StorEdge 3511 FC Array (SATA) with sccli 1.6.2 or later


Modification History
Date: 12-OCT-2005

12-Oct-2005:

  • Updated Contributing Factors and Resolution sections, re-release as Resolved

 



Previously Published As
101568
Internal Comments


From engineering:



Should a data mismatch occur specifically due to incorrectly changing optimization modes, please consult Sun for assistance as the data might be recovered through a series of complex processes performed only by highly trained personnel.



Upcoming CLI release 1.6.2 will prevent the user from changing the cache optimization mode while there is an existing LD. The user must delete all LDs before the optimization mode can be changed, and the CLI will also prompt the user to reset the controller after the mode is changed and before new LDs are created. 1.6.2 contains the fix for the 3310. Current release as of this writing is 2.1.1.



Furthermore, a future 4.0 controller firmware release has the section of code rewritten so that different mode LDs can exist in a controller, thus making problem nonexistent.



 


Internal Contributor/submitter
kevin.l.doan@sun.com

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
neill.wood@sun.com

Internal Services Knowledge Engineer
david.mariotto@sun.com

Internal Escalation ID
1-3226737

Internal Sun Alert Kasp Legacy ID
101568, 57644 (Sun Alert)

Internal Sun Alert & FAB Admin Info
Critical Category: Data Loss, Availability ==> Pervasive
Significant Change Date: 2004-09-15, 2005-10-12
Avoidance: Upgrade, Workaround
Responsible Manager: bagher.vahdatinia@sun.com
Original Admin Info: [WF 12-Oct-2005, Dave M: upgrade sccli released, waited a long time for engineering to agree on clarification of this issue. Re-release as Resolved]
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: 57644
Synopsis: Changing the Cache Optimization Mode Incorrectly on Sun StorEdge 3310, 3510, 3511 May Cause Issues Affecting Filesystem Availability and Data Integrity
Category: Availability, Data Loss
Product: Sun StorEdge 3310, 3510, 3511 Arrays
BugIDs: 5069625
Avoidance: Workaround
State: Committed
Date Released: 15-Sep-2004
Date Closed:
Date Modified:
Escalation IDs: 1-3226737
Pending Patches:
Resolution Patches:
FIN:
FCO:
Date Submitted: 14-Sep-2004
Submitter: kevin.l.doan@sun.com
Responsible Engineer: neill.wood@sun.com
Responsible Manager: bagher.vahdatinia@sun.com
CTE group: PTS NWS US
Responsible Writer: david.mariotto@sun.com
Distribution: Contract SunSolve

Workflow History:

WF State: Issued, 15-Sep-2004, David Mariotto
WF Note: sending for release OK by PTS

WF State: Draft, 15-Sep-2004, David Mariotto
WF Note: sent for review 9/14

WF State: Draft, 14-Sep-2004, David Mariotto
WF Note: Article created.

Exported from KMS Creator Sat May 21 09:13:15 2005 GMT, olaf.reineke@sun.com
Internal SA-FAB Eng Submission
Changing the Cache Optimization Mode Incorrectly on Sun StorEdge 3310, 3510 or 3511 May Cause Issues Affecting Filesystem Availability and Data Integrity

Product_uuid
3db30178-43d7-4d85-8bbe-551c33040f0d|Sun StorageTek 3310 SCSI Array
58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array
9fdbb196-73a6-11d8-9e3a-080020a9ed93|Sun StorageTek 3511 SATA Array

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