Sun Storage 3510 FC Array
 
Sun Storage 3511 SATA Array
 

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
 

When upgrading from 3.27x to 4.11I and using Logical Volumes (LV) in a Storedge 3510FC array or 3511FC array (SATA), the system will experience the following issue: data sent to the Logical Volume in the array will not destage from cache to the logical volume(s), resulting in loss of access to the array and possible loss of data. 

This issue can occur on the following platforms:

• Sun StorEdge 3510 FC array with firmware revision 4.11I and without firmware revision 4.13c (as delivered in patch 113723-11)
• Sun StorEdge 3511 FC array (SATA) with firmware revision 4.11I and without firmware revision 4.13c (as delivered in patch 113724-05)

This issue is seen immediately after the firmware upgrade from 3.27x to 4.11I.

Notes:

1. Only existing 3.27x Logical Volumes are affected.
2. New Logical Volumes created on 4.11I do not experience this issue.
3. Logical partitions and logical drives do not experience this issue.
4. An array upgraded to 4.11I WITHOUT Logical Volumes does not experience this issue.

Following the firmware upgrade from 3.27x to 4.11I, access to the array will be lost. I/O sent to the Logical Volumes while the array was at 4.11I may be lost or corrupted.

To work around the described issue, one of the two following remedies can be used (use only one of these workarounds):

A) For use prior to an upgrade (recommended):

Note: This is a preventative measure when using Logical Volumes on a 3510FC or 3511FC with SATA that is to be upgraded. Follow these steps:

1. Back up data existing on the Logical Volume(s) to tape or to a filesystem which is not located on the array being updated.
2. Remove the Logical Volume.
3. Upgrade the firmware using normal procedures listed in the upgrade patch README file.
4. Recreate the Logical Volumes on the upgraded array.
5. Restore the data from the remote location or tape.

B) If the condition already exists:

Note: This procedure should be used to recover access to the array after an upgrade to 4.11I and seeing access and cache issues.

1. To gain access to the array, the firmware must be downgraded to the latest 3.27x firmware.
2. Use fsck(1M) to check the filesystem before mounting.
3. When the data is checked and available, workaround "A" could be used to upgrade to 4.11I.

This issue is addressed on the following platforms:

• Sun StorEdge 3510 FC array with firmware revision 4.13c (as delivered in patch 113723-11 or later)
• Sun StorEdge 3511 FC array (SATA) with firmware revision 4.13c (as delivered in patch 113724-05 or later)

30-Sep-2005:

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

References

While the ability to create and manage logical volumes remains a feature of Sun StorEdge 3000 family arrays for legacy reasons, the size and performance of physical and logical drives have made the use of logical volumes obsolete. Logical volumes are unsuited to some modern configurations and do not work in those configurations. In particular, the use of logical volumes is not supported in Sun Cluster environments. Please refer to StorEdge 3000 documents for more information.

References

This solution has no attachment