Document fins/I0557-2
FIN #: I0557-2
SYNOPSIS: Differences in LUN Capacity after Firmware Upgrade on StorEdge A3000
or RSM2000 Hardware Raid Controllers.
DATE: May/23/00
KEYWORDS: Differences in LUN Capacity after Firmware Upgrade on StorEdge A3000
or RSM2000 Hardware Raid Controllers.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Differences in LUN Capacity after Firmware Upgrade on
StorEdge A3000 or RSM2000 Hardware Raid Controllers.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: RM6.1.1 Firmware
PRODUCT CATEGORY: Storage / SW Admin; Software / Unbundled
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- Anysys - System Platform Independent -
X-Options Affected
------------------
X6530A - - RSM2000 in Exp. Cabn. 15x4.2Gb/5400 -
X6531A - - RSM2000 in Exp. Cabn. 35x4.2Gb/5400 -
X6532A - - RSM2000 15*4.2GB/7200 FWSCSI -
X6533A - - RSM2000 35*4.2GB/7200 FWSCSI -
X6534A - - A3000 15*9.1GB/7200 FWSCSI -
X6535A - - A3000 35*9.1GB/7200 FWSCSI -
X6536A - - RSM Array 2000 -
X6536A - - StorEdge A3000 -
X6537A - - StorEdge A3000 -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
798-0522-0X RAID Manager6.1.1 -
REFERENCES:
BugId: 4252057, 4173298
Patch: 108555-0X
ESC: 521367, 522672
MANUAL: 805-4057-11 Sun StorEdge RAID Manager 6.1.1 User's Guide
MANUAL: 805-3656-11 Sun StorEdge RAID Manager 6.1.1 Release Notes
MANUAL: 805-4058-11 Sun StorEdge RAID Manager 6.1.1 Installation
and Support Guide for Solaris
URL:http://storageweb.eng.sun.com/techmark_site/arrays/dilbert/DacStore.note
PROBLEM DESCRIPTION:
==============================================================
In this -2 update to FINI0557-1, the Raid controller F/W using
Raid Manager 6.22 or later version procedure has been added to
the item #4 on the CORRECTIVE ACTION. No other updates are
required
==============================================================
After a RM6.1.1 upgrade the customer will notice that the A3000 or
RSM2000 LUNs created with Raid Manager firmware 2.5.2 are smaller in
capacity than LUNs created prior to the upgrade even though the drive
groups show the same size. This condition will be seen when the LUNs
created and use the maximum available capacity in the drive group.
Another problem is that the customers might notice a newly replaced
disk drive has 38MB less data capacity then other drives in the same
LUN provided.
This LUN was created under RM6.1 or lower.
Example shown below:
-------------------------------------------------------------------------
Group Information for rb011_001
Group No. of RAID No. of Total Remaining
LUNs Level Drives Space(MB) Space(MB)
Hot Spare - - 1 - -
1 1 5 5 34541 0
2 1 5 5 34389 0
3 1 5 5 34541 0
4 1 5 5 34541 0
5 1 5 5 34541 0
6 1 5 5 34541 0
7 1 5 4 25905 0
-------------------------------------------------------------------------
Upon further investigation, it has been noted that Raid Manager
firmware 2.5.2 or higher requires 40MB of DacStore disk space per
drive, while Raid Manager firmware 2.4.4.1 or earlier requires 2MB of
DacStore disk space. Thus, the 4+1 raid 5 LUN created in drive group 2
after the RM6.1.1 upgrade is 152MB less than the other same raid level
LUNs created before the RM6.1.1 upgrade.
If a LUN is carried over from prior to RM6.1.1 upgrade and later a disk
drive in the LUN has to be replaced, the replacement drive would come up
with the 40MB DacStore space, and therefore has a smaller data capacity.
This will effect full LUNs or LUNs that are mirrored, possibly preventing
access to all the data.
IMPLEMENTATION:
---
| | MANDATORY (Fully proactive)
---
---
| X | CONTROLLED PROACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
The following recommendation is provided as a guide line for authorized
Enterprise Services Field Representatives and Enterprise Customers that
may be at risk of encountering the above mentioned problem;
To calculate the expected capacity difference in a LUN, follow the
equation: 38MB x number of data disks.
1. Customers should be made aware of the DacStore size difference before
they upgrade to RM6.1.1. Customers should back up data and re-create
the LUNs during the upgrade to avoid future problems with DacStore.
2. If a customer did not re-build the LUNs during RM6.1.1 upgrade, but
later creates new LUNs, then wishes to expand the existing file system
size with the new LUNs, it is recommended that the customer recreate
the old LUNs to make the LUN size uniform.
3. How to identify a LUN created prior to RM6.1.1 upgrade.
If previously upgraded from earlier versions of RAID Manager to RAID
Manager 6.1.1/firmware 02.05.02.xx, it is possible to verify the
Dacstore size by doing some simple calculations as shown below. If
the Dacstore size is verified to be 2MB, it is recommended that the
customer back up their data then re-configure the LUNs to 40MB
Dacstore if possible.
Dacstore size = Raw disk capacity Disk data capacity
i) Find the raw disk capacity on a drive.
Select Configuration --> Module --> Profile Drives.
The Module Profile screen displays detailed drive information for
the RAID module you selected on the Configuration screen. Raw disk
capacity on each drive is displayed under "Capacity" in megabytes
(MB).
ii) Find the data capacity per drive.
Select Configuration.
The Configuration Application main screen displays the total capacity
of each drive group under "Total" in megabytes (MB).
Data capacity per drive= Total capacity of a drive group/Number of data
disks
The number of data disks= Number of drives in a RAID 0 drive group.
The number of data disks= Number of drives minus 1 in a RAID 3 drive group.
The number of data disks= Number of drives minus 1 in a RAID 5 drive group.
4. Workaround to bring the replacement drive up with 2MB DacStore.
If a customer does not wish to back up the data to re-configure the LUN
and the customer is running one of the RM6.1.1 releases, a workaround
is to install patch 
108555 or greater.
Note: This patch is not publicly available. However it can be obtained
through the escalation process. Also, this patch will not alter
DACstore size on existing LUNs. For example, if the array contains
LUNs with 40MB DACstore and then the patch is applied, and later a
disk drive in that LUN needs to be replaced, that LUN's DACstore
will remain at 40MB.
This patch contains a special release Raid controller firmware version
that allows user to bring up a replacement disk drive with 2MB Dacstore
size. This solution will not help customers who want to eventually
upgrade to RM 6.22 or later. When downloading this special Raid controller
FW using Raid Manager GUI, a user will receive the following message:
The file selected for downloading are not compatible with current firmware
versions on the controllers. "OK or CANCEL".
This is a normal message and the user has to press OK to proceed with the
FW download.
5. Occasionally when deleting old RM6.1 LUN's then recreating the LUNs with
RM6.1.1, the 38MB DacStore region may appear as "Remaining Capacity"
after
the LUN has finished formatting. When creating the LUN, the size cannot
be increased in order to utilize this "extra" capacity.
A reboot will clear the "extra" remaining capacity.
COMMENTS:
Concerning item 5 above, the correct LUN capacity reporting feature has been
verified in RM6.22.
--------------------------------------------------------------------------
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services Documenta-
tion" and click on "FIN & FCO attachments", then choose the
appropriate
folder, FIN or FCO. This will display supporting directories/files for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------
SunWeb Home SunWeb Search SunSolve Home Simple Search
Sun Proprietary/Confidential: Internal Use Only
Feedback to SunSolve Team
Copyright (c) 1997-2003 Sun Microsystems, Inc.