- Solaris (SPARC, X86, X64) 자료실 -

순간을 위해 평생을 준비하라.
기회란 언제나 예고 없이 찾아온다 항상 낚싯대를 던져 놓아라.
전혀 기대하지 않았던 곳에서 고기가 잡히리라.




Vote Reply Modify Forward Prev Next List

  작성자   : 조성환 [ ladmin ] 추천: 3882, 조회: 18687, 줄수: 164, 분류: Etc.
Inaccessible Periods of High Sequential Writes(강추)

출처 : http://sunsolve.sun.com/search/document.do?assetkey=1-26-101771-1



Synopsis: Certain Sun SCSI and FC-AL Disk Drives May Become Inaccessible During Periods of High Sequential Writes

Category: Availability

Product: Solaris 9 Operating System, Solaris 10 Operating System, Solaris 8 Operating System

BugIDs: 6272112

Avoidance: Patch

State: Resolved

Date Released: 27-Jul-2005, 01-Jul-2005

Date Closed: 27-Jul-2005

Date Modified: 13-Jul-2005, 27-Jul-2005, 09-Aug-2005, 08-May-2006, 30-Aug-2006



1. Impact
Certain Sun SCSI and FC-AL disk drives (listed below) may become inaccessible during periods of high sequential writes.

2. Contributing Factors
This issue can occur on the following disk drives:

LVD Ultra-320 SCSI:

DK32EJ36N (390-0111) without patch 116369-10
DK32EJ72N (390-0108) without patch 116370-10
DK32EJ14N (390-0155) without patch 116512-06
HUS10143A (390-0179) without patch 116512-06
HUS10733A (390-0176) without patch 116370-10
FC-AL:

DK32EJ36F (390-0146) without patch 116463-02
DK32EJ72F (390-0117) without patch 116464-02
DK32EJ14F (390-0120) without patch 116465-02
HUS1073FA (390-0167) without patch 120400-02
HUS1014FA (390-0173) without patch 120401-02
The described issue only occurs if all of the following conditions are met:

1. One or more of the above disks are being used internally in supported hosts, or in JBOD configurations. This issue does not occur when the disk is installed in a controller-based RAID array such as the StorEdge A1000, SE3120 or SE3310.

2. The disk has a firmware version older than PQ0F or PA05 (on SCSI disk drives), or 2Q0J or 2A08 (on FC-AL disk drives).

3. The disk is subjected to a large number of sequential writes, such as an SVM resync or large sequential database write.

4. The host's SCSI patch is at one of the versions listed below:

SPARC Platform

Solaris 8 with patch 108974-43 or later
Solaris 9 with patch 112834-06 or later
Solaris 10 with patch 118992-01 or later
x86 Platform

Solaris 8 with patch 116982-02 or later
Solaris 9 with patch 115874-04 or later
Solaris 10 with patch 118993-01 or later
Note: The issue addressed in this Sun Alert is not caused by the above SCSI patches. The issue is the result of a code bug in the above drives' firmware which, in certain instances (those listed above), can be triggered by the above versions of the SCSI patch.

To determine if a system is equipped with a drive type listed above, run the "iostat -En" command as shown in the following example:

   % iostat -En
   c1t0d0    Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
   Vendor: <NAME>  Product: DK32EJ72FSUN72G  Revision: 0207 Serial No:
   0242B09QD1
   Size: 73.40GB <73400057856 bytes>
   Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
   Illegal Request: 0 Predictive Failure Analysis: 0
To determine the firmware revision of a drive, do the following:

Run the "format" utility as root.
Choose a disk from "AVAILABLE DISK SELECTIONS".
Run "inquiry" from "FORMAT MENU".
Output will appear that is similar to the following:

   Vendor:   <Vendor Name>
   Product:  DK32EJ72FSUN72G
   Revision: 2Q0J


3. Symptoms
Should the described issue occur, disks which have become inaccessible will appear in the Solaris "format" utility as "drive type unknown" and messages similar to the following will appear in "/var/adm/messages" file:

 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@18,600000/pci@1/scsi@2/sd@6,0 (sd6):
 May 11 02:24:52 <hostname>        Error for Command: write(10)               Error Level: Retryable
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  Requested Block: 125321424     Error Block: 125321424
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  Vendor:            Serial Number: 0323W14P82
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  Sense Key: Unit Attention
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  ASC: 0x29 (<vendor unique code 0x29), ASCQ: 0x1, FRU: 0x0
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@18,600000/pci@1/scsi@2/sd@6,0 (sd6):
 May 11 02:24:52 <hostname>        Error for Command: write(10)               Error Level: Retryable
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  Requested Block: 125321424      Error Block: 125321424
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  Vendor:            Serial Number: 0323W14P82
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  Sense Key: Not Ready
 May 11 02:24:52 <hostname> scsi: [ID 107833 kern.notice]  ASC: 0x4 (<vendor unique code 0x4), ASCQ: 0x1, FRU: 0x0
 May 11 02:24:57 <hostname> scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@18,600000/pci@1/scsi@2/sd@6,0 (sd6):
 May 11 02:24:57 <hostname>        Error for Command: write(10)               Error Level: Retryable
 May 11 02:24:57 <hostname> scsi: [ID 107833 kern.notice]  Requested Block: 125321424      Error Block: 125321424
 May 11 02:24:57 <hostname> scsi: [ID 107833 kern.notice]  Vendor:            Serial Number: 0323W14P82
 May 11 02:24:57 <hostname> scsi: [ID 107833 kern.notice]  Sense Key: Not Ready
 May 11 02:24:57 <hostname> scsi: [ID 107833 kern.notice]  ASC: 0x4 (<vendor unique code 0x4), ASCQ: 0x1, FRU: 0x0
 May 11 02:25:02 <hostname> scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@18,600000/pci@1/scsi@2/sd@6,0 (sd6):
 May 11 02:25:02 <hostname>        Error for Command: write(10)                Error Level: Retryable
 May 11 02:25:02 <hostname> scsi: [ID 107833 kern.notice]  Requested Block: 125321424       Error Block: 125321424
 May 11 02:25:02 <hostname> scsi: [ID 107833 kern.notice]  Vendor:             Serial Number: 0323W14P82
 May 11 02:25:02 <hostname> scsi: [ID 107833 kern.notice]  Sense Key: Hardware Error
 May 11 02:25:02 <hostname> scsi: [ID 107833 kern.notice]  ASC: 0x44 (internal target failure), ASCQ: 0x0, FRU: 0x0




Solution Summary Top

4. Relief/Workaround
An immediate workaround for a disk that has entered this inaccessible state is to remove and re-insert the disk according to the procedure relevant to the corresponding operating system and hardware environment. The disk should again become usable.



5. Resolution
To resolve this issue, the firmware of the drives listed below should be upgraded to the following minimum levels:

LVD Ultra-320 SCSI (firmware version PQ0F and PA05)

DK32EJ36N with patch 116369-10 or later
DK32EJ72N with patch 116370-10 or later
DK32EJ14N with patch 116512-06 or later
HUS10143A with patch 116512-06 or later
HUS10733A with patch 116370-10 or later
FC-AL (firmware version 2Q0J and 2A08)

DK32EJ36F with patch 116463-02 or later
DK32EJ72F with patch 116464-02 or later
DK32EJ14F with patch 116465-02 or later
HUS1073FA with patch 120400-02 or later
HUS1014FA with patch 120401-02 or later


Change History
13-Jul-2005:
Updated Contributing Factors section
27-Jul-2005:
State: Resolved
Updated Contributing Factors, Relief/Workaround, and Resolution sections
09-Aug-2005:
Updated Contributing Factors and Relief/Workaround sections
08-May-2006:
Updated Contributing Factors and Resolution sections
30-Aug-2006:
Updated Contributing Factors and Resolution sections
This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.


Copyright 2000-2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


이전: ODBC [open database connectivity] 정의
다음: 있지도 않은 페이지가 호출되어 로그에 쌓일때
2006/10/30(09:27) from 203.234.120.78
CrazyWWWBoard 2000

Vote Reply Modify Forward Prev Next List

(c) Nobreak Technologies, Inc.