Release Notes

Table 23. Fixed Storage Management Issues in Storage Center 7.4.2
Issue Description
SCOS-57359 A controller might reset if Storage Center returns a null pointer to an associated virtualization
volume or hypervolume.
SCOS-56244 A controller might reset because of a memory leak.
SCOS-56076 A controller might reset because of issues with metadata paging.
SCOS-55944 Attempting to clear a disk spare hunger alert on a Storage Center might fail when the only
remaining hungry device is deleted.
SCOS-55897 On a dual-controller storage system with two ports per fault domain, volumes might become
unaccessible if a customer performs the following actions:
1. A customer disables a switch port that is connected to a controller port in a fault domain.
2. A customer performs a port rebalance on the Storage Center.
3. A customer disables a switch port that is connected to the other controller port that is in
the same fault domain as the port from step 1.
4. A customer reenables the switch port from step 1.
5. A customer reenables the switch port from step 3.
SCOS-55835 A controller might reset at the same time on multiple days because the Storage Center fails to
skip null pointers when dequeuing IORPs from the delay queue.
SCOS-55713 View volumes cannot be created on a Storage Center if a user creates a traffic profile of the
type Group with a name that starts with text 'Default'.
SCOS-55468 On a dual-controller storage system that is being updated from Storage Center version 7.1 or
earlier to Storage Center 7.3, a scrubbing RAID device may adopt the wrong Reed-Solomon
attribute during the update.
SCOS-55267 SNMP is unable to retrieve information about the power supply and cooling fan modules on
SC7020, SC5020, and SCv3000 series storage systems.
SCOS-55147 A controller might reset because of a background process that attempts to communicate with
a subcomponent that no longer exists in Storage Center.
SCOS-55136 On SCv2000 series and SC4020 storage systems, a controller might reset because of a
cache-to-flash restore error.
SCOS-54981 On a dual-controller storage system, the SCSI target cannot handle persistent reservations
requests for volumes that are active on the other controller.
SCOS-54737 Restriping pagepool devices might take longer to complete for storage systems that were
originally deployed with Storage Center 5.5 or earlier.
SCOS-54696 When a storage system that is low on available disk space is updated from a version of Storage
Center that does not support Distributed Sparing to a version of Storage Center that does
support Distributed Sparing, the Storage Center might attempt to create more spare space
when no space is available.
SCOS-54626 Storage Center might fail to remove pagepool devices that are marked as space optimized.
SCOS-54597 A controller might reset because of errors in memory accounting routines.
SCOS-54592 A RAID restripe might become stuck if there is not enough space to create a new device in the
tier where devices are getting replaced.
SCOS-54172 Storage Center RAID devices might become over degraded if writes to multiple disks fail
around the same time.
SCOS-54122 When drives are added to a storage system, pagepool devices may not be correctly marked for
pruning.
SCOS-53504 A controller might reset if there is an issue deleting uninitialized http request because of
connectivity issues that prevent the storage system from sending the http request.
16