Vdisk Failure on a Sun StorEdge 6130 May Cause All the Volumes on the Same Controller to Become Inaccessible |
|
| Category : | Availability |
| Release Phase : | Resolved |
| Product : | Sun StorageTek 6130 Array
|
| Bug Id : | 6292076
|
| Date of Workaround Release : | 10-AUG-2005
|
| Date of Resolved Release : | 23-MAR-2006
|
Impact
Vdisk failure on a Sun StorEdge 6130 array may cause volumes on healthy vdisks located on the same controller to become inaccessible.
Contributing Factors
This issue can occur on the following system:
on the following platforms:
SPARC Platform
x86 Platform
Note: Fiber Channel configuration is not supported on Solaris 8 or Solaris 9 on the x86 platform.
Symptoms
If the described issue occurs, messages similar to the following will be seen upon vdisk failure:
Jun 23 10:01:39 xxx scsi: [ID 107833 kern.warning] WARNING:
/scsi_vhci/ssd@g600a0b800017b043000016b142691bc1 (ssd17):
Jun 23 10:01:39 xxx Error for Command: write(10) Error Level:
Retryable
Jun 23 10:01:39 xxx scsi: [ID 107833 kern.notice] Requested Block:
123739552 Error Block: 123739552
Jun 23 10:01:39 xxx scsi: [ID 107833 kern.notice] Vendor: SUN
Serial Number:
Jun 23 10:01:39 xxx scsi: [ID 107833 kern.notice] Sense Key:
Hardware Error
Jun 23 10:01:39 xxx scsi: [ID 107833 kern.notice] ASC: 0x84
(<vendor> unique code 0x84 ), ASCQ: 0x0, FRU: 0x0
In the above example, "ssd17" is the RAID0 volume which is unavailable upon a disk failure. "0x84/0x0" indicates the requested command or "Mode Select" operation is not allowed with the logical unit in this state.
When this occurs, the current behavior of the target driver is that it keeps resetting the target which is on the controller. As a result, the volumes hosted on the controller from all the other vdisks get reset.
The above messages are followed by messages similar to the following:
Jun 23 10:01:39 xxx scsi: [ID 243001 kern.warning] WARNING:
/ssm@0,0/pci@18,600000/SUNW,qlc@1/fp@0,0 (fcp0):
Jun 23 10:01:39 xxx FCP: WWN 0x200500a0b817aff0 reset
successfully
Workaround
There is no workaround. Please see the "Resolution" section below.
Resolution
This issue is addressed in the following release:
SPARC Platform:
x86 Platform
Modification HistoryDate: 17-NOV-2005
- State: Resolved
- Updated Contributing Factors, Relief/Workaround, and Resolution sections
Date: 27-FEB-2006
- Changed State from "Resolved" to "Workaround"
- Updated Contributing Factors, Relief/Workaround, and Resolution sections
Date: 23-MAR-2006
- State: Resolved
- Updated Contributing Factors, Relief/Workaround, and Resolution sections
AttachmentsThis solution has no attachment