Symptoms
There is currently no patched or fixed DDOS version for this issue.Root cause has been determined & workaround has been provided.Fix will be worked into future DDOS releases.Symptoms:
DD6300 system is upgraded from 7-disks to 12-disks.Additional 5-disks are installed & added (#storage add) to the Active Tier successfully.When the #filesys expand command is entered a false reading of 2.18TiB is reported as the available capacity to be expanded.The upgrade is expected to increase capacity from ~14.5 TiB to ~24 TiB.
Affected Systems:
DD6300All DDOS versions Note: Other All-in-One systems could encounter this issue if cache tier disks are used in the Head/Controller unit.
Cause
This issue is encountered due to a misread capacity value within DDOS.During the #filesys expand command the system scans through all the disks of the head unit to determine the smallest (ppart) partition in use.The smallest in the case of a DD6300 happens to be the SSD (Cache Tier) - with a ppart size of 745.22 GiB.Rough calculation would be as follows:Out of 5 newly added disks 2 disks are parity.Therefore:745.22Gib *3 = 2235.66 GIB2235.66 /1024 = 2.18 TiB (i.e. The number we are showing as max expandable)
Resolution
Workaround:This is a reporting error and the false (2.18TiB) capacity value may be safely disregarded.Continue with #filesys expand and accept (Yes) when prompted.
Example:
1.) Disks are installed & present an 'Unknown' status, as expected, with #disk show state:
eos-t2# ddsh disk show state
Enclosure Disk
1 2 3 4 5 6 7 8 9 10 11 12 13 14
--------- -------------------------------------------
1 . . . s . . . U U U U U . .
--------- -------------------------------------------
2.) Disks are successfully added to the Active Tier using #storage add disks 1.8 1.9 1.10 1.11 1.12 tier active
The 5x new disks have a SPARE status:
sysadmin@eos-ps-t2-2# disk show state
Enclosure Disk
1 2 3 4 5 6 7 8 9 10 11 12 13 14
--------- -------------------------------------------
1 . . . s . . . s s s s s . .
--------- -------------------------------------------
3.) The final step (#filesys expand) reports that the Filesys capacity will be increased by only 2.18TiB (instead of an expected ~11TiB):
sysadmin@eos-t2# filesys expand
The filesystem will be expanded approximately by 2.18 TiB.
Are you sure? (yes|no) [no]: yes
ok, proceeding.
########################################### [100%]
The approximate size of the filesystem is 23.87 TiB.
sysadmin@eos-t2#
