Asset ID:	1-77-1001260.1
Update Date:	2011-03-01
Keywords:

---

Solution Type  Sun Alert Sure

Solution  1001260.1 :   Logical Drive Initialization or Parity Checks on a Sun StorEdge 3510 FC Array May Take a Very Long Time  


PreviouslyPublishedAs
201708

Product
Sun StorageTek 3510 FC Array

Bug Id
<SUNBUG: 4889104>

Date of Resolved Release
22-JUL-2003

Impact

On a Sun StorEdge 3510 FC Array, parity checks or Logical Drive (LD) initialization may take a very long time (up to 12 hours) if there is an active telnet session to the array.

Contributing Factors

This issue can occur in the following releases:

SPARC Platform

• Sun StorEdge 3510 FC Array with firmware revision 3.27K or lower (patch 113723-02)

Notes: The described issue will only occur when there is an active telnet session to the Sun StorEdge 3510 FC Array. Other remote array management tools (e.g. serial connections to the array) will not cause the described issue. An array's current firmware revision can be determined by logging into the array by means of a telnet or serial connection and selecting "view system information" from the menu.

Symptoms

Should the descibed issue occur, initialization of a Logical Drive (LD) on a Sun StorEdge 3510 FC Array will take more than 4 hours with an active telnet connection to the array. Also, paritiy checks will take a very long time when a telnet connection to the array is active. No error messages are generated.

Workaround

To work around this issue, close the telnet session, and avoid using telnet to access the Sun StorEdge 3510 Array. Manage the array using sccli (Sun StorEdge 3XX0 Command Line Interface), sscs (Sun StorEdge 3XX0 Configuration Service Console) or a serial connection.

Resolution

This issue is addressed in the following releases:

SPARC Platform

• Sun StorEdge 3510 FC Array with firmware revision 3.27M or later (available in patch 113723-03)

Modification History

References

<SUNPATCH: 113723-03>

Previously Published As
101297
Internal Comments

This bug occurs due to the CPU being saturated by ethernet processes negotiating the term type for the telnet session. Therefore it may affect parity regenerations as well.

You may be experiencing this bug if you have started an initialization of an LD and it is taking longer than 4 hours. For example, a 3x73gGb drive RAID 5 taking 4 hours for initialization is much more alarming than a 12x146Gb drive RAID 5 with the same build time. Logical Drive initialization exact times cannot be predicted.

Factors that will affect drive initialization time include: RAID type, number of drives, drive capacity, and I/O load. Long drive initialization times, plus an open telnet session may be indicative of the problems outlined in the bug.

Internal Contributor/submitter
[email protected]

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
[email protected]

Internal Services Knowledge Engineer
[email protected]

Internal Escalation ID
546566

Internal Resolution Patches
113723-03

Internal Sun Alert Kasp Legacy ID
101297, 55901 (Sun Alert)

Internal Sun Alert & FAB Admin Info
Critical Category: Availability ==> Pervasive
Significant Change Date: 2003-07-22
Avoidance: Patch, Workaround
Responsible Manager: [email protected]
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: 55901
Synopsis: Logical Drive Initialization or Parity Checks on a Sun StorEdge 3510 FC Array May Take a Very Long Time
Category: Availability
Product: Sun StorEdge 3510 FC Array
BugIDs: 4889104
Avoidance: Workaround, Patch
State: Resolved
Date Released: 22-Jul-2003
Date Closed: 22-Jul-2003
Date Modified:
Escalation IDs: 546566
Pending Patches:
Resolution Patches: 113723-03
FIN:
FCO:
Date Submitted: 18-Jul-2003
Submitter: [email protected]
Responsible Engineer: [email protected]
Responsible Manager: [email protected]
CTE group: CPRE NWS US
Responsible Writer: [email protected]
Distribution: Public SunSolve

Workflow History:

WF State: Issued, 22-Jul-2003, Pete Stauffer
WF Note: Received signoff from Youana Sarkis.
Sent for release.

WF State: Draft, 22-Jul-2003, Pete Stauffer
WF Note: Received signoff from Youana Sarkis.
Sent for release.

WF State: Draft, 22-Jul-2003, Pete Stauffer
WF Note: Sent for signoff.

WF State: Draft, 21-Jul-2003, Pete Stauffer
WF Note: Sent for sunalert review.

WF State: Draft, 18-Jul-2003, Pete Stauffer
WF Note: Article created.

Exported from KMS Creator Sat May 21 09:02:04 2005 GMT, [email protected]
Internal SA-FAB Eng Submission
Logical Drive Initialization or Parity Checks on a Sun StorEdge 3510 FC Array May Take a Very Long Time

Product_uuid
58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array

References

SUNPATCH:113723-03

Attachments

This solution has no attachment