Abstract: Provided are techniques for spare device management. Candidate devices are sorted into spare coverage groups by type. One or more candidate devices having closest fitting characteristics of a desired type are identified from the spare coverage groups. The identified one or more candidate devices are assigned to be spare devices for the spare coverage group. It is determined whether a desired number of spare devices have been assigned to the spare coverage group. In response to determining that the desired number of spare devices have not been assigned, a spare device having the closest fitting characteristics for every predetermined number of candidate devices having the closest fitting characteristics is assigned, until the desired number of spare devices having the closest fitting characteristics are assigned.

Abstract: A radio frequency identifier (RFID) active/passive tag is provided to identify failed sub-CRU and location within a higher level CRU. When an error occurs on the base blade or within one of the sub-CRUs, the embedded processor writes failure information to the RFID. RFID tags may also contain data identifying the locations, of the sub-CRUs of the blade. Thus, when there is a failure, the RFID may report the failed component as well as the location of a failed sub-CRU. Sub-CRUs may also include an embedded processor and RFID tag. When a service action is initiated to repair or replace a blade, the RFID tag may be read by a RFID reader. The RFID reader device may then present failure information, including the identification of the failed sub-CRU and other associated information to the operator. The RFID reader device may also request associated information from a server computer.

Abstract: An apparatus, system, and method are disclosed for preventing write starvation in a storage controller with access to low performance storage devices. A storage device allocation module is included to assign a storage device write cache limit for each storage device accessible to a storage controller. The storage device write cache limit comprises a maximum amount of write cache of the storage controller available to a storage device for a write operation. At least one storage device comprises a low performance storage device and a total amount of storage available to the storage devices comprises an amount greater than a total storage capacity of the write cache. A low performance write cache limit module is included to set a low performance write cache limit. The low performance write cache limit comprises an amount of write cache available for use by the at least one low performance storage device for a write operation.

Abstract: A method, system and computer program product for minimizing read response time in a storage subsystem including a plurality of resources is provided. A middle logical block address (LBA) is calculated for a read request. A preferred resource of the plurality of resources is determined by calculating a minimum seek time based on a closest position to a last position of a head at each resource of the plurality of resources, estimated from the middle LBA. The read request is directed to at least one of the preferred resource or an alternative resource.

Abstract: An apparatus, system, and method are disclosed for presenting a storage volume as a virtual volume. An attribute module determines a primary volume physical attribute of a primary volume. A presentation module presents the primary volume physical attribute to a host as a target volume virtual attribute of a target volume. A translation module translates communications between a host and the target volume. In one embodiment, a copy module creates a point-in-time copy of the primary volume on the target volume.

Abstract: An apparatus, system, and method are disclosed for selective cross communications between autonomous storage modules. A RAID controller communicates through a first cascading communications loop comprising a first storage module. The first storage module includes a plurality of storage devices and is disposed in an enclosure. The RAID controller also communicates through a second cascading communications loop comprising a second storage module. The second storage module also includes a plurality of storage devices and is disposed in the enclosure. An interface module transmits messages of the first loop through the second storage module. In one embodiment, the RAID controller communicates a cross communications command to the interface module through the second storage module to enable the interface module to transmit the messages of the first loop through the second storage module in response to a failure of the first loop upstream of the first storage module.

Abstract: An apparatus, system, and method are disclosed for providing a redundant array of inexpensive disks (“RAID”) storage subsystem within a processor blade enclosure. A first RAID controller blade is included and configured to fit in a processor blade enclosure. At least one processor in communication with the first RAID controller blade is included. A disk enclosure blade is provided that includes a plurality of hard disk drives. The disk enclosure blade is configured to fit in the processor blade enclosure and the hard disk drives are in communication with the first RAID controller blade.

Abstract: An apparatus for parity data management receives a write command and write data from a computing device. The apparatus also builds a parity control structure corresponding to updating a redundant disk array with the write data and stores the parity control structure in a persistent memory buffer of the computing device. The apparatus also updates the redundant disk array with the write data in accordance with a parity control map and restores the RAID controller parity map from the parity control structure as part of a data recovery operation if updating the redundant disk array with the write data is interrupted by a RAID controller failure resulting in a loss of the RAID controller parity map. In certain embodiments, the parity control structure is a RAID controller parity map.

Abstract: A method is disclosed to provide power to a plurality of data storage devices disposed in a data storage system. The data storage system comprises a system controller comprising a data storage device power-up algorithm and a plurality of data storage devices, where each of the plurality of data storage devices cannot automatically provide a device present signal. The method detects the presence of each of the plurality of data storage devices, and then provides power to each of the detected data storage devices using the data storage device power-up algorithm.

Abstract: An apparatus, system, and method are disclosed for integrating an enclosure. An initialization module initializes a second enclosure. A discovery module discovers a connection of the second enclosure to a first enclosure. An address module creates a valid address for the second enclosure. An assignment module assigns the address to the second enclosure. A power control module cycles power to the second enclosure to reinitialize the second enclosure and set the address.

Abstract: A method is disclosed to reconfigure a storage array disposed in a data storage system. The method supplies a data storage system comprising a plurality of data storage devices, wherein each of the plurality of data storage devices is assigned to one of a plurality of data storage arrays, or is assigned as a spare device. The method then detects an unassigned data storage device, and determines if any of the plurality of data storage arrays comprises a degraded data storage array. If the method determines that any of the plurality of data storage arrays comprises a degraded data storage array, then the method determines if the unassigned data storage device can be used to restore the degraded data storage array to optimal reliability, optimal performance, and optimal efficiency.

Abstract: A plurality of storage devices of a plurality of types is provided. A plurality of criteria is associated for each of the plurality of storage devices, based on characteristics of the plurality of storage devices, wherein the plurality of criteria can be used to determine whether a selected storage device is a compatibility spare for a storage device in a storage device array, and whether the selected storage device is an availability spare for the storage device in the storage device array. A determination is made by a spare management application, based on at least the plurality of criteria and at least one optimality condition, of a first set of storage devices selected from the plurality of storage devices to be allocated to a plurality of storage device arrays, and of a second set of storage devices selected from the plurality of storage devices to be allocated as spares for the plurality of storage device arrays.

Abstract: Consistency for replicating data storage subsystem configurations in accordance with a “golden” configuration file. A data storage subsystem comprises a blade system with a plurality of slots, the blade system configured to support a plurality of blades and a storage system, each arranged in a predetermined slot of the blade system. The storage system arranges a logical configuration of the server blades in accordance with a “golden” configuration file. The server blade slot versus WWN information is collected and provided to the storage system. The storage system converts the “golden” configuration file slot information to WWNs. The server blades are enabled for access to said storage system as they log on with WWNs in accordance with the “golden” configuration file.

Abstract: A sector conversion device includes a non-volatile memory area that is used to save two sectors' worth of data when power is lost during the sector conversion process. These two sectors of data are stored in the non-volatile memory area within the sector conversion device itself. The non-volatile memory within the sector conversion device is connected to the main internal memory of the device by a special link that is wider than the normal word size of the buffer. When power is lost to the storage enclosure during a scenario where data is being written to the hard disk drives, which involves sector conversion, the internal processor of the sector conversion device immediately initiates a transfer from the volatile buffer queue memory to the non-volatile memory. The information that is transferred (hardened) is the two sectors of data that were involved in the sector conversion process.

Abstract: Consistency for replicating data storage subsystem configurations in accordance with a “golden” configuration file. A data storage subsystem comprises a blade system configured to support a plurality of blades and a storage system, each arranged in a predetermined slot of the blade system, and at least one zoneable switch whose zoning is disabled at power on. A management module operates the blade system to power on all slots. The storage system, in accordance with a “golden” configuration file, transfers port enablement sequencing to the switch, and the switch enables and zones ports in sequence to allow the server blades to see the storage system in accordance with the port enablement sequence. The storage system is configured with the “golden” configuration file to log on the server blades in accordance with the port enablement sequence to logically configure the server blades in accordance with the “golden” configuration file.

Abstract: Consistency for replicating data storage subsystem configurations in accordance with a “golden” configuration file. A data storage subsystem comprises a blade system with a plurality of slots, the blade system configured to support a plurality of blades and a storage system, each arranged in a predetermined slot of the blade system. A management module operates the blade system to first power on the storage system, and subsequently to power on the plurality of server blades in a sequential order that matches a blade system natural boot sequence order, skipping the storage system, and the storage system is configured with the “golden” configuration file to log on the server blades in accordance with the power on sequence to logically configure the server blades in accordance with the “golden” configuration file.

Abstract: Consistency for replicating data storage subsystem configurations in accordance with a “golden” configuration file. A data storage subsystem comprises a blade system with a plurality of slots, the blade system configured to support a plurality of blades and a storage system, each arranged in a predetermined slot of the blade system. A management module operates the blade system to first power on the storage system. In accordance with a “golden” configuration file, the storage system passes sequence information to the management module. The management module powers on the plurality of server blades in accordance with the sequence information. The storage system is configured with the “golden” configuration file to log on the server blades in accordance with the power on sequence to logically configure the server blades in accordance with the “golden” configuration file.

Abstract: An apparatus, system, and method are disclosed for maintaining dynamic persistent data. A selection module selects the most recent metadata. A verification module verifies that the metadata has been successfully updated. A validation module validates that the metadata is accurate. A communication module communicates the Persistent Storage Device data to a system processor if the metadata is validated. A storage module may store primary and secondary information of data, metadata, and data state variables.

Abstract: Provided are a method, system, and article of manufacture for error checking addressable blocks in storage. Addressable blocks of data are stored in a storage in stripes, wherein each stripe includes a plurality of data blocks for one of the addressable blocks and at least one checksum block including checksum data derived from the data blocks for the addressable block. A write request is received to modify data in one of the addressable blocks. The write and updating the checksum are performed in the stripe having the modified addressable block. An indication is made to perform an error checking operation on the stripe for the modified addressable block in response to the write request, wherein the error checking operation reads the data blocks and the checksum in the stripe to determine if the checksum data is accurate. An error handling operation is initiated in response to determining that the checksum data is not accurate.

Abstract: A system and method for thresholding system power loss notifications in a data processing system are provided. Power loss detection modules are provided in a data processing system having one or more data processing devices, such as blades in an IBM BladeCenter® chassis. The power loss detection modules detect the type of infrastructure of the data processing system, a position of a corresponding data processing device within the data processing system, and a capability of the data processing system to provide power during a power loss scenario. The detection module detects various inputs identifying these types of data processing system and power system characteristics and provides logic for defining a set of behaviors during a power loss scenario, e.g., behaviors for sending system notifications of imminent power loss. The detection of the various inputs and the defining of a set of behaviors may be performed statically and/or dynamically.