After a RM6.1.1 upgrade the customer will notice that the A3000/A3500 LUNs
created with FW2.5.2 are smaller in capacity than LUNs created prior to the
upgrade eventhough the drive groups show the same size. This condition will
be seen when the LUNs created use the maximum available capacity in the
drive group. This is because that FW 2.5.2 or higher requires 40MB of
DacStore disk space per drive while FW2.4.4.1 or earlier requires 2MB of
DacStore.
See example 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
-------------------------------------------------------------------------
The 4+1 raid 5 LUN created in drive group 2 after RM6.1.1 upgrade is
152MB less than the other same raid level LUNs created before the RM6.1.1
upgrade. To calculate the expected capacity difference, follow the
equation: 38MB x number of data disk.
If a customer created new LUNs after RM6.1.1 upgrade and wanted to expand
the existing file system size with this new LUN, it is recommended that the
customer recreated the old LUNs to make the LUN size uniform.
Occasionally, when delete old RM6.1 LUN's then recreate the LUNs with RM6.1.1,
the 38Mb DacStore region may appears as "Remaining Capacity" after the LUN
has finished formatting. When you create the LUN you can not increase it's
size to utilise this "extra" capacity. A reboot will clear the "extra"
remaining capacity.
Correct Lun capacities reporting have been verified under the future
release of RM6.2.